- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
",t};e.buildCustomizationMenuUi=t;function n(e){let t='
",t}function s(e){let n=e.filter.currentValue||e.filter.defaultValue,t='${e.filter.label}
`,e.filter.options.forEach(s=>{let o=s.id===n;t+=``}),t+="${e.filter.label}
`,t+=`access_entry_arn
Type: STRING
Provider name: accessEntryArn
Description: The ARN of the access entry.
account_id
Type: STRING
cluster_name
Type: STRING
Provider name: clusterName
Description: The name of your cluster.
created_at
Type: TIMESTAMP
Provider name: createdAt
Description: The Unix epoch timestamp at object creation.
kubernetes_groups
Type: UNORDERED_LIST_STRING
Provider name: kubernetesGroups
Description: A name
that you’ve specified in a Kubernetes RoleBinding
or ClusterRoleBinding
object so that Kubernetes authorizes the principalARN
access to cluster objects.
modified_at
Type: TIMESTAMP
Provider name: modifiedAt
Description: The Unix epoch timestamp for the last modification to the object.
principal_arn
Type: STRING
Provider name: principalArn
Description: The ARN of the IAM principal for the access entry. If you ever delete the IAM principal with this ARN, the access entry isn’t automatically deleted. We recommend that you delete the access entry with an ARN for an IAM principal that you delete. If you don’t delete the access entry and ever recreate the IAM principal, even if it has the same ARN, the access entry won’t work. This is because even though the ARN is the same for the recreated IAM principal, the roleID
or userID
(you can see this with the Security Token Service GetCallerIdentity
API) is different for the recreated IAM principal than it was for the original IAM principal. Even though you don’t see the IAM principal’s roleID
or userID
for an access entry, Amazon EKS stores it with the access entry.
tags
Type: UNORDERED_LIST_STRING
type
Type: STRING
Provider name: type
Description: The type of the access entry.
username
Type: STRING
Provider name: username
Description: The name
of a user that can authenticate to your cluster.