Release v0.11.2

Changes included in v0.11.2:

🚀 Features

• [feature] [developer] add RoleRef support #137: Adding support in the lib to reference RoleRefs in the ClusterAccess reconciler.
• [feature] [user] cluster- and access-request names #134: - Prevent name conflicts for ClusterRequests and AccessRequests
• [feature] [user] package crds in component #133: Package the custom ressource definition manifests for the openmcp-operator into the OCM component
• [feature] [operator] install providers in system namespace #126: Install all providers in a common namespace "openmcp-system"
• [feature] [operator] Allow override for 'run' and 'init' command in providers #129: The init and run commands for providers can now be overwritten by using the respective fields in the spec of ServiceProvider, ClusterProvider, and PlatformService` resources.

🔧 Chores

• [breaking] [operator] remove onboarding cluster kubeconfig argument #130: The openmcp-operator now takes a --kubeconfig argument for the platform cluster kubeconfig instead of the previous --platform-cluster argument. The --onboarding-cluster argument has been removed to make the operator work without an existing onboarding cluster.

Release v0.11.1

Changes included in v0.11.1:

🚀 Features

• [feature] [user] add RoleRefs to AccessRequest API ##128: Adding support for role references in AccessRequests to bind the ServiceAccount to an existing role or cluster role.
• [feature] [operator] use K8sNameUUID instead of K8sNameHash and let each mcp have its own namespace ##114: The library functions regarding stable MCP namespace and request names have been adapted to use the new UUID-style hash functions and the concept of each MCP having its own namespace on the platform cluster.

Release v0.11.0

Changes included in v0.11.0:

🚀 Features

• [feature] [user] add ExtraVolumes and ExtraVolumeMounts to DeploymentSpec #118: Adding ExtraVolumes and ExtraVolumeMounts fields to the DeploymentSpec
• [feature] [user] add name field to AccessRequest permissions #113: It is now possible to overwrite the name of (Cluster)Roles generated by AccessRequests.
• [feature] [operator] add extra scopes to oidc provider config #108: It is now possible to specify additional scopes for OIDC providers (in AccessRequest and ManagedControlPlane api types).
• [feature] [user] add ManagedControlPlane API #104: Added the ManagedControlPlane type with api version core.openmcp.cloud/v2alpha1 and added OIDC configuration to the AccessRequest type.

🐛 Fixes

• [bugfix] [user] add ExtraVolumes and ExtraVolumeMounts to DeploymentSpec #118: Fixing permission issues on ClusterProfiles during Init job of Cluster Providers and Service Providers

🔧 Chores

• release v0.11.0 #120.
• [bugfix] [operator] remove broken validation rule #111: Removed a broken validation rule that made it impossible to apply the AccessRequest CRD.
• [breaking] [user] rename v2 MCP resource #109: The v2 ManagedControlPlane resource has been renamed to ManagedControlPlaneV2 to avoid k8s trying to convert between v1 and v2, since we want to use both in parallel for the migration period.

Release v0.10.0

Changes included in v0.10.0:

🚀 Features

• [feature] [developer] args and envs ##99: - Change of the arguments and environment variables that are passed to providers.
• [feature] [user] minor api enhancements #100: ClusterRequest resources can now be configured to delay the removal of their own finalizer (therefore also delaying their own deletion) until the corresponding Cluster is gone when the request is deleted, instead of the finalizer being removed immediately after the deletion of the Cluster has been triggered. Cluster providers need to take care to implement the feature accordingly. The spec.waitForClusterDeletion flag has no effect in situations where deletion of the ClusterRequest does not trigger a deletion of the corresponding Cluster.
• [feature] [developer] minor api enhancements #100: ServiceProvider resources must now expose a list of their service resource types in their status. Service providers must take care to implement the feature accordingly. This serves as a kind of 'service catalog' that allows to look up the k8s resources that belong to a specific service provider.

🔧 Chores

• [feature] [operator] release v0.10.0 #101: - Release v0.10.0 of the openmcp operator

🐛 Fixes

• [fix] [user] empty AccessRequestConfig during controller start up #96: Fixing possible nil pointer dereference bug while accessing empty AccessRequestConfig during start up of accessrequest controller

Release v0.9.1

Changes included in v0.9.1:

🐛 Fixes

• fix wrong reference type in Cluster type #90.

Release v0.9.0

Changes included in v0.9.0:

🔨 Refactoring

• use common Status #86.

🔧 Chores

• renovate updates go lang version #72.
• adapt cluster config reference struct #73: The .spec.clusterConfigRef field in the Cluster resource has been changed. It was originally designed with apiVersion and kind, but since the referenced profile already determines the provider that is responsible for the Cluster, these values are not needed, as the provider knows the expected type of the cluster configuration (and can only handle that type).
• add common api package #79.
• allow a Cluster to reference multiple cluster configurations #82.

🐛 Fixes

• fix ObjectReference common struct #84.

Release v0.8.3

Changes included in v0.8.3:

🔧 Chores

• release v0.8.3 #64: NONE

🐛 Fixes

• use correct permissions in workload access request #63:

Release v0.8.2

Changes included in v0.8.2:

🔧 Chores

• Release v0.8.2 #62:

Release v0.8.1

CHANGELOG.md

Release v0.7.0

Feature

• feat: add apiserver endpoint to generic Cluster status: #35
• feat: improve deployment controller: #32
• feat: reuse common workflows: #38
• feat: add library module: #37

Fix

• fix: prevent removing clusterRef or requestRef from AccessRequest: #34
• fix(deps): update module sigs.k8s.io/controller-runtime to v0.21.0: #28
• fix(deps): update module github.com/openmcp-project/controller-utils to v0.9.0: #30

Other

• Extend deployment spec: environment variables and logging verbosity: #29
• add log output for debugging: #33
• cleanup labels: #36
• chore: enables renovate update of submodules: #20
• chore: release v0.7.0: #40