-
Notifications
You must be signed in to change notification settings - Fork 19
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
Issue with installation using the operator no action set #106
Comments
I can't reproduce this with either v0.5.3 or the a custom installation using the latest on main with a beta.1 porter agent. Can you check the image used on the porter operator pod and make sure that it's the version you expect? I sometimes run into problems where an older deployment isn't removed completely and the operator pod isn't running the desired version of the code. Here's what I have after installing v0.5.3 (which corresponds to ghcr.io/getporter/porter-operator@sha256:93e1c6d7b6dc8074b915ce50d09231ee5ea05bcdf43082c1c91e9b532d353b13 for the operator's image). Note that it ran Only really old versions of the operator from the first POC ran
|
Closing for now as I built a new k8s cluster and am not seeing this now. |
When using operator v0.5.2 or v0.5.3 I am seeing failures due to the
--action
parameter not being set.The output in the intaller pod is as follows:-
This was on a new k8s installation with a brand new porter operator installation.
The installation file used was :-
The text was updated successfully, but these errors were encountered: