https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# fleet
a
This message was deleted.
👍 1
n
Thanks for that! How do you use this command? From inside the fleet-agent pod or...?
b
in your code's workspace, with a working kubectl config
👍 1
if you change to the directory of the fleet.yaml, it should render everything
cc; @careful-piano-35019 (because I think you care about fleet)
👏 2
f
That’s awesome!
c
@brave-afternoon-4801 pinned to channel
🚀 1
f
I hope I don't ruin your weekend but look at the release notes of v0.10.0: https://github.com/rancher/fleet/releases/tag/v0.10.0-rc.4 Additions • Deprecate "fleet test" command, previously used to debug chart by @manno in #2113
b
WHYYYYYYYYY
@careful-piano-35019 Seriously, can we get that reverted??
@creamy-pencil-82913 Sorry to pull you in, but this channel is like screaming into a void. Is there any way to get some attention on this?
I kind of understand why they made an option to be bundle-centric, but I have no idea why that justifies killing an existing and useful command.
s
How do you run fleet on the cmdline in rancher?
b
Hey, 
fleet test
doesn’t work very well. It’s not going to vanish soon, but it’s deprecated.
However, ‘fleet test’ doesn’t look at actual clusters. Furthermore, when called with 
-f
, it doesn’t use the bundlereader, so the default target is not added. Actually a lot of processing is missing.
We recently added two new commands 
target
and 
deploy
. 
target
looks at the actual cluster and prints the results. 
deploy
has a dry run option, so you can preview what would happen. Together with 
apply
(https://www.suse.com/c/rancher_blog/fleet-multi-cluster-deployment-with-the-help-of-external-secrets/) you should be able to use Fleet without the controllers, if you wanted to. If you want to test them, documentation can for now be found in https://github.com/rancher/fleet/issues/2110 and the CLI reference I just generated, e.g.: https://fleet.rancher.io/cli/fleet-cli/fleet_target
I don’t think any of that is included in Rancher yet, but you could download the binaries from our release candidate over at https://github.com/rancher/fleet/releases/tag/v0.10.0-rc.4
b
Okay, while 
test
may not have done this level of processing, doesn't this now introduce a dependency on a running cluster? Where is target deriving inputs?
s
Thank you for the reply. Are you saying that I can use that binary against a rancher cluster? I just use my kubeconfig against it?
b
I finally have a week to touch this cluster again. Looking ...
sooo, 
target
always requires 
-b
.. I'm sure there is a technical reason that I don't understand for this change, but .. 😞
target
requires a file?
and if 
deploy
catches an issue, it outputs the yaml and the error message to the same steam (stderr) 😞
i'm thankful that 
test
was only deprecated to start. thank you.
For example, this is the header on the rendered 
deploy
output:
Copy code
2024/04/08 08:33:21 warning: cannot overwrite table with non table for rancher-logging.fluentd.tolerations (map[])
And like, I get it, the upstream chart has mixed up values, but the output should be split up std out/err
3 Views
Open in Slack
PreviousNext
Powered by