k3s introduction #127
Merged
k3s introduction #127
Conversation
This file contains hidden or 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
|
mbenguig
approved these changes
Mar 14, 2025
fviale
pushed a commit
that referenced
this pull request
Mar 26, 2025
* labelNodes k3s * application deployment update * wait for master update * Update docker-compose env var * documentation and deployment update (cherry picked from commit 9cedd76)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Supporting the cluster deployment to use instead of the k8s, also k3s version.
K8s remains as the default. Versioning is passed over the CLUSTER_TYPE environmental variable.
it was tested with k3s and dedicated workflow is created properly PA jobs 2093/94.
by default it runs k8s version like before and was tested only with aws as there should not be much imact PA jobs 2098-2105), will be tested again when on nebulous sandbox