Open pbochynski opened 10 months ago
Would love to test it at earliest convinience.
This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
If you think that I work incorrectly, kindly raise an issue with the problem.
/lifecycle stale
The goal would be to allow kyma users to deploy apps (and run tests ) on the provisioned kyma runtimes in the CI jobs .
Execution can be divided into several stages:
OIDC configuration will be included in the gardener provisioning in q2 https://github.com/kyma-project/control-plane/issues/3316#issuecomment-1963822606
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
Kyma Infrastructure Manager (KIM) should apply Operator-Facing OIDC separately from User-facing OIDC(s)
In order to allow this we need to adjust the interfaces: 1) User -> Kyma Environment Broker (KEB)
User should be able to define requiedClaims (key-value pairs)
2) KEB -> KIM
additionalOidcConfigs
additionalOidcConfigs[0]
with the default User-facing OIDC configoidcConfig
with Operator-facing OIDC 3) KIM -> Gardener
shoot-oidc-service
extension in shoot CR4) KIM -> Kyma
authentication.gardener.cloud/v1alpha1/OpenIDConnect
objects in kyma based on additionalOidcConfigs
to avoid unwanted impersonations, we should:
Regarding migration from existing shoots to Runtime CRs
.
oidcConfig
<- Populate withoidcConfig
additionalOidcConfigs
<- Populate as the first entry withoidcConfig
Would be great to have this available soon, as a dependency we want to use requires that and also to bring our kya into production it would be kind of a prerequisite.
Description Enable the option to trust the additional identity provider compliant with OpenID. The provider can be registered in the Kyma cluster and kubernetes API server will authenticate tokens that match the provider issuer. The complete solution should allow to establish the trust during the provisioning so the cluster can be accessed from fully automated processes (without user presence). To accomplish that the following changes are required:
shoot-oidc-service
extension for shoot clustersOpenIDConnect
resource in the shoot cluster as Kyma instance parameter (KEB)Acceptance Criteria
Reasons Many users request a possibility to deploy software to freshly creaated Kyma clusters in automated way. Changing the default IDP for the cluster is the only solution available for now, but then IDP has to support both human users and service accounts what is usually challenging. With additional OIDC provider it can be used only for system to system authorization and will be much easier to set up.
Links