-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature: add BYOID support for OCI artifacts and Helm charts #1121
Conversation
There is no dependency for this PR. It is ready for another look. |
0c4ef9a
to
0157f3e
Compare
6a2f1d9
to
b862af2
Compare
9f27814
to
4615898
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: janetkuo, sdowell The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This commit integrates BYOID support into Config Sync by supporting a new auth type for OCI and Helm: `k8sserviceaccount`. It requires GKE or Fleet Workload Identity to be enabled. The KSA along with WI will be exchanged to a federated token which can be used to authenticate to Ubermint-enabled GCP services directly.
/lgtm |
1d50f52
into
GoogleContainerTools:main
…ontainerTools#1121) This commit integrates BYOID support into Config Sync by supporting a new auth type for OCI and Helm: `k8sserviceaccount`. It requires GKE or Fleet Workload Identity to be enabled. The KSA along with WI will be exchanged to a federated token which can be used to authenticate to Ubermint-enabled GCP services directly.
…ontainerTools#1121) This commit integrates BYOID support into Config Sync by supporting a new auth type for OCI and Helm: `k8sserviceaccount`. It requires GKE or Fleet Workload Identity to be enabled. The KSA along with WI will be exchanged to a federated token which can be used to authenticate to Ubermint-enabled GCP services directly.
…ontainerTools#1121) This commit integrates BYOID support into Config Sync by supporting a new auth type for OCI and Helm: `k8sserviceaccount`. It requires GKE or Fleet Workload Identity to be enabled. The KSA along with WI will be exchanged to a federated token which can be used to authenticate to Ubermint-enabled GCP services directly.
…ontainerTools#1121) This commit integrates BYOID support into Config Sync by supporting a new auth type for OCI and Helm: `k8sserviceaccount`. It requires GKE or Fleet Workload Identity to be enabled. The KSA along with WI will be exchanged to a federated token which can be used to authenticate to Ubermint-enabled GCP services directly.
…ontainerTools#1121) This commit integrates BYOID support into Config Sync by supporting a new auth type for OCI and Helm: `k8sserviceaccount`. It requires GKE or Fleet Workload Identity to be enabled. The KSA along with WI will be exchanged to a federated token which can be used to authenticate to Ubermint-enabled GCP services directly.
This commit integrates BYOID support into Config Sync by supporting a new auth type for OCI and Helm: `k8sserviceaccount`. It requires GKE or Fleet Workload Identity to be enabled. The KSA along with WI will be exchanged to a federated token which can be used to authenticate to Ubermint-enabled GCP services directly.
This commit integrates BYOID support into Config Sync by supporting a new auth type for OCI and Helm:
k8sserviceaccount
. It requires GKE or Fleet Workload Identity to be enabled. The KSA along with WI will be exchanged to a federated token which can be used to authenticate to Ubermint-enabled GCP services directly.