Update ProviderDockerEE to ProviderMKE across codebase #4147
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates all references of
ProviderDockerEEtoProviderMKEthroughout the codebase to reflect the rebranding of Docker Enterprise Edition to Mirantis Kubernetes Engine (MKE).Changes Made
ProviderDockerEEconstant toProviderMKEinapi/v1/installation_types.goIsDockerEE()method toIsMKE()Backward Compatibility
This change maintains full backward compatibility:
"DockerEnterprise"to preserve CRD compatibility"DockerEnterprise"continue to work unchangedFiles Changed
api/v1/installation_types.go- Core API definitionspkg/controller/installation/core_controller.go- Installation controller logicpkg/controller/k8sapi/k8s-endpoint.go- K8s API endpoint handlingpkg/controller/utils/discovery.go- Provider discovery logicpkg/render/node.go- Node rendering with MKE-specific configurationspkg/render/applicationlayer/applicationlayer.go- Application layer renderingpkg/render/compliance.go- Compliance component renderingpkg/render/logstorage/eck/eck.go- ECK log storage renderingTesting
All existing tests continue to pass, confirming that:
This change improves code clarity by using the current product name while maintaining full compatibility with existing deployments.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
get.helm.shcurl -fsSL --retry 5 REDACTED(dns block)If you need me to access, download, or install something from one of these locations, you can either:
This pull request was created as a result of the following prompt from Copilot chat.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.