You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Bevel ansible scripts install outdated dependencies, such as aws, helm, flux, vault ...
The install does not work for me using these.
Describe the solution you'd like
Update versions installed by playbook setup tasks
Describe alternatives you've considered
Install latest, and copy over to referenced bin directory (what i have done)
or
Remove the install scripts and simply check for pressence.
Additional context
Installing the latest versions myself and copying over to ~/bin works for me both on MacOS (apple silicon) and on Ubuntu (24.04)
Updated flux_version from 2.3.0 --> 2.4.0 in setup_k8s_environment (otherwise flux bootstrap will throw an error when run)
I am also using latest HashiCorp vault (external), however also successfully connected in prior test to both a localhost vault, and a vault on same cluster. The documentation mentions to use <= a quite old version, which i found is not necessary (at least with ansible playbooks).
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Bevel ansible scripts install outdated dependencies, such as aws, helm, flux, vault ...
The install does not work for me using these.
Describe the solution you'd like
Update versions installed by playbook setup tasks
Describe alternatives you've considered
Install latest, and copy over to referenced bin directory (what i have done)
or
Remove the install scripts and simply check for pressence.
Additional context
Installing the latest versions myself and copying over to ~/bin works for me both on MacOS (apple silicon) and on Ubuntu (24.04)
Updated flux_version from 2.3.0 --> 2.4.0 in setup_k8s_environment (otherwise flux bootstrap will throw an error when run)
I am also using latest HashiCorp vault (external), however also successfully connected in prior test to both a localhost vault, and a vault on same cluster. The documentation mentions to use <= a quite old version, which i found is not necessary (at least with ansible playbooks).
The text was updated successfully, but these errors were encountered: