Initial implementation #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bastjan
force-pushed
the
initial-implementation
branch
from
822d55d to
39cf5a2
Compare
bastjan
force-pushed
the
initial-implementation
branch
from
39cf5a2 to
ee760ff
Compare
HappyTetrahedron
approved these changes
Oct 29, 2024
|
🚀 This PR has been released as Triggering workflows 🛠️ Auto tagging enabled with label |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a deployment for the cloudscale provider. The cloudscale provider then manages the machines and a separate deployment for the missing OpenShift components like the MachineSet controller.
The service account is bound to the
cluster-adminrole since it needs all permissions of the target MachineSet/* controllers and all permissions a provider requires.The PR contains an alert that fires if managing the MachineSet controller deployment fails.
Checklist
changelog.
The PR has a meaningful description that sums up the change. It will be
linked in the changelog.
bug,enhancement,documentation,change,breaking,dependencyas they show up in the changelog.