-
-
Notifications
You must be signed in to change notification settings - Fork 462
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BREAKING] Config File Enhancements: v1alpha3, migrations, generic k3s-args #605
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
iwilltry42
added
enhancement
New feature or request
priority/high
breaking change
scope/cli
Issue concerns the CLI (cmd/)
scope/package
pkg/
labels
May 14, 2021
iwilltry42
force-pushed
the
enhancement/k3s-args-nodefilter
branch
2 times, most recently
from
May 14, 2021 10:48
1b89fee
to
cef3b17
Compare
- new version v1alpha3 with k3s extraArgs using node filters - reflected in CLI via --k3s-arg - new migration option to migrate (internally and via cli) from v1alpha2 to v1alpha3 - enhancements to how config files are being read - e2e tests for config file migration
iwilltry42
force-pushed
the
enhancement/k3s-args-nodefilter
branch
from
May 14, 2021 10:53
cef3b17
to
abb5506
Compare
iwilltry42
commented
May 14, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
double checked
iwilltry42
changed the title
[XXL] Config File Enhancements: v1alpha3, migrations, generic k3s-args
[BREAKING] Config File Enhancements: v1alpha3, migrations, generic k3s-args
May 14, 2021
iwilltry42
referenced
this pull request
May 14, 2021
iwilltry42
added a commit
that referenced
this pull request
Jun 16, 2021
…s-args (#605) Excerpt: - new version v1alpha3 with k3s extraArgs using node filters - reflected in CLI via --k3s-arg - new migration option to migrate (internally and via cli) from v1alpha2 to v1alpha3 - enhancements to how config files are being read - e2e tests for config file migration
iwilltry42
added a commit
that referenced
this pull request
Jun 28, 2021
…s-args (#605) Excerpt: - new version v1alpha3 with k3s extraArgs using node filters - reflected in CLI via --k3s-arg - new migration option to migrate (internally and via cli) from v1alpha2 to v1alpha3 - enhancements to how config files are being read - e2e tests for config file migration
iwilltry42
added a commit
that referenced
this pull request
Jul 6, 2021
…s-args (#605) Excerpt: - new version v1alpha3 with k3s extraArgs using node filters - reflected in CLI via --k3s-arg - new migration option to migrate (internally and via cli) from v1alpha2 to v1alpha3 - enhancements to how config files are being read - e2e tests for config file migration
iwilltry42
added a commit
that referenced
this pull request
Jul 9, 2021
…s-args (#605) Excerpt: - new version v1alpha3 with k3s extraArgs using node filters - reflected in CLI via --k3s-arg - new migration option to migrate (internally and via cli) from v1alpha2 to v1alpha3 - enhancements to how config files are being read - e2e tests for config file migration
somaritane
referenced
this pull request
in AbsaOSS/k3d-action
Nov 15, 2021
- k3d config examples migrated to `apiVersion: k3d.io/v1alpha3` [https://github.com/rancher/k3d/pull/605](https://github.com/rancher/k3d/pull/605) - `:direct` node filter option used when load balancer is disabled [https://github.com/rancher/k3d/pull/656](https://github.com/rancher/k3d/pull/656) - `--label` --> `--runtime-label` [https://github.com/rancher/k3d/pull/598](https://github.com/rancher/k3d/pull/598) - `--k3s-server-arg` --> `--k3s-arg` with server node filter (`@server:*`) [https://github.com/rancher/k3d/pull/605](https://github.com/rancher/k3d/pull/605) - Updated documentation Signed-off-by: Timofey Ilinykh <ilinytim@gmail.com>
somaritane
referenced
this pull request
in AbsaOSS/k3d-action
Nov 15, 2021
- k3d config examples migrated to `apiVersion: k3d.io/v1alpha3` [https://github.com/rancher/k3d/pull/605](https://github.com/rancher/k3d/pull/605) - `:direct` node filter option used when load balancer is disabled [https://github.com/rancher/k3d/pull/656](https://github.com/rancher/k3d/pull/656) - `--label` --> `--runtime-label` [https://github.com/rancher/k3d/pull/598](https://github.com/rancher/k3d/pull/598) - `--k3s-server-arg` --> `--k3s-arg` with server node filter (`@server:*`) [https://github.com/rancher/k3d/pull/605](https://github.com/rancher/k3d/pull/605) - Updated documentation Signed-off-by: Timofey Ilinykh <ilinytim@gmail.com>
somaritane
referenced
this pull request
in AbsaOSS/k3d-action
Nov 16, 2021
- k3d config examples migrated to `apiVersion: k3d.io/v1alpha3` [https://github.com/rancher/k3d/pull/605](https://github.com/rancher/k3d/pull/605) - `:direct` node filter option used when load balancer is disabled [https://github.com/rancher/k3d/pull/656](https://github.com/rancher/k3d/pull/656) - `--label` --> `--runtime-label` [https://github.com/rancher/k3d/pull/598](https://github.com/rancher/k3d/pull/598) - `--k3s-server-arg` --> `--k3s-arg` with server node filter (`@server:*`) [https://github.com/rancher/k3d/pull/605](https://github.com/rancher/k3d/pull/605) - removed `disableImageVolume` option from examples and test assets - Updated documentation Signed-off-by: Timofey Ilinykh <ilinytim@gmail.com>
somaritane
referenced
this pull request
in AbsaOSS/k3d-action
Nov 16, 2021
- k3d config examples migrated to `apiVersion: k3d.io/v1alpha3` [https://github.com/rancher/k3d/pull/605](https://github.com/rancher/k3d/pull/605) - `:direct` node filter option used when load balancer is disabled [https://github.com/rancher/k3d/pull/656](https://github.com/rancher/k3d/pull/656) - `--label` --> `--runtime-label` [https://github.com/rancher/k3d/pull/598](https://github.com/rancher/k3d/pull/598) - `--k3s-server-arg` --> `--k3s-arg` with server node filter (`@server:*`) [https://github.com/rancher/k3d/pull/605](https://github.com/rancher/k3d/pull/605) - removed `disableImageVolume` option from examples and test assets - Updated documentation Signed-off-by: Timofey Ilinykh <ilinytim@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
breaking change
enhancement
New feature or request
priority/high
scope/cli
Issue concerns the CLI (cmd/)
scope/package
pkg/
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.
to v1alpha3
Details
Legend:
CLI (
cmd/
)--k3s-server-arg
and--k3s-agent-arg
become--k3s-arg
with node filter supportk3d config migrate INPUT [OUTPUT]
command to migrate config files between versions (currently only to most recent versionv1alpha3
)Module (
pkg/
)Config
interface typev1alpha3
is the new defaultoptions.k3s.extraserverargs|extraagentargs
foroptions.k3s.extraArgs
with node filter supportFromViperSimple
for config loading specifically tailored toSimple
style config and now we only use the genericFromViper
which also selects the correct version given the inputV1alpha2
tov1alpha3
)K3sServerArgs
andK3sAgentArgs
fromClusterCreateOpts
, as they're now injected on individual node levelMisc
v1alpha3
config version