Closed villasenor closed 1 year ago
Did you get to the bottom of this, also facing same issue, as well as using same branch as you (k3s by any chance?)
I haven't had a chance to come back to it yet @prom3theu5, but glad I'm not the only one seeing this! My guess is that the changes made in the branch fixed it enough for the Kubernetes API to not flat out reject the config, but the operator likely needs some code changes to parse the new config format properly. For what it's worth, I don't think k8s vs k3s should make a difference here as k3s is a Certified Kubernetes distribution :)
@villasenor or @prom3theu5 are you still facing this issue with the most recent release we made of the Operator (1.3.0 at the time of this writing)?
I don't have the test env setup for this anymore. Was there a specific code change you made that you feel could have fixed this issue @dogonthehorizon?
Hi @villasenor. A new version of Operator was released by Armory (the company @dogonthehorizon and I work for). That new version included code changes that we anticipate would have fixed your problem.
I see. Well if I get around to trying this scenario again I'll definitely report back here! Thanks!
Sounds great, thanks @villasenor ! We'll close this issue for now but if you do still run into this issue please re-open or file a new issue :D
First, I should note that I'm using Kubernetes 1.23.1. The Spinnaker Operator
master
branch currently will not deploy on 1.23.1, so I'm using this PR branch: https://github.com/armory/spinnaker-operator/pull/250Other than that, everything is standard.
Following this guide: https://github.com/armory/spinnaker-operator#example-1-basic-install
I constructed a
SpinnakerService
that looks like this:However, no matter what I do, the operator still thinks I haven't set a version. I tried to track down the offending code, but I got lost. Any help here would be much appreciated!
Operator error logs: