Skip to content
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

Fix: allow commas in kubelet arg values #135

Merged
merged 17 commits into from
Jan 12, 2024

Conversation

jessebot
Copy link
Collaborator

@jessebot jessebot commented Jan 12, 2024

Fixes #132 by adding tabs to the k3s and k3d screen to specifically add kubelet args, instead of accepting them as part of the k3s.yaml file. New TUI screenshot:

Screenshot of smol-k8s-lab TUI k3s config screen showing the bottom box now has a tab for k3s yaml and a tab for kubelet args

The button at the bottom of the third box that says "➕ K3s Option" now can distinguish which tab and section of the yaml it needs to update. When a user enters kubelet-arg as a new option for the k3s.yaml tab, it will gracefully just switch to the correct kubelet args tab.

@jessebot jessebot added the k3s label Jan 12, 2024
@jessebot jessebot self-assigned this Jan 12, 2024
  • Updating jinja2 (3.1.2 -> 3.1.3)
  • Updating markdown (3.5.1 -> 3.5.2)
  • Updating google-auth (2.26.1 -> 2.26.2)
  • Updating pycryptodome (3.19.1 -> 3.20.0)
@jessebot jessebot marked this pull request as ready for review January 12, 2024 09:50
@jessebot
Copy link
Collaborator Author

test is failing on k3s, but that's due to a lack of isolation of the environments, I think. Will investigate that in a separate issue/PR

@jessebot jessebot merged commit 2d9370f into main Jan 12, 2024
1 of 2 checks passed
@jessebot jessebot deleted the fix/issue-132-commas-in-kubelet-arg-values branch January 12, 2024 13:44
jessebot added a commit that referenced this pull request May 15, 2024
…let args into their own tab (#135)

* don't create a list if there's = in the kubelet-arg

* adding more comprehensive kubeletConfig class

* clean up k3s/k3d borders for last tui block

* tui: clean up tabs and borders for k3s.yaml and kubelet args specifically

* change trigger to tab, and add k3s kubelet + k3s k3s_yaml as potential tabs

* fix issue where we kept writing the kubelet arg even if it already existed

* specify an id for the kubelet widget so that we can generate rows for it

* update dependencies:
  • Updating jinja2 (3.1.2 -> 3.1.3)
  • Updating markdown (3.5.1 -> 3.5.2)
  • Updating google-auth (2.26.1 -> 2.26.2)
  • Updating pycryptodome (3.19.1 -> 3.20.0)

* add doc strings for action_launch_new_option_modal and method

* switch to max-pods everywhere instead of max_pods

* updating docs example of configfile

* refactor DistroConfigScreen.action_launch_new_option_modal, update screenshots everywhere

* update alt text for distro_config_screen.svg in docs

* update test-smol-k8s-lab to run on pull request instead of pushes

* add tests for k3s

* remove branches-ignore: ['main'] for test smol-k8s-lab job

* if kubelet-arg is new option for k3s_yaml, exit and switch to the kubelet args tab for k3s tabbedcontent
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

🐛 Selecting "New Cluster" causes distro section of configfile to be overwritten
1 participant