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
I set size in 5 in CR
--> deployment size is 5
--> 5 pods
I manually change deployment size to 2 (memcached) <-- started at around 40 sec
--> now changed to 2 pods
--> CR still with size in 5
I expect: the deployment of the memachecd should become 5 by the Operator due to the CR is 5
--> but still stuck in 2
Expected - After deployment changes, it should reconcile and match it with CR
What did you expect to see?
It must reconcile and match Deployment state to CR - User defined state.
What did you see instead? Under which circumstances?
Nothing happened and Cluster contains updated Deployment state.
Environment
Kubernetes cluster type:
Minikube
$ operator-sdk version
openjdk version "16.0.2" 2021-07-20
OpenJDK Runtime Environment (build 16.0.2+7-67)
OpenJDK 64-Bit Server VM (build 16.0.2+7-67, mixed mode, sharing)
laxmikantbhaskarpandhare@lpandhar-mac memcached-quarkus-operator % operator-sdk version
operator-sdk version: "v1.14.0-11-g3d61d762-dirty", commit: "3d61d762ea0ac9926afc0b30042e35f257becad2", kubernetes version: "v1.21", go version: "go1.17.2", GOOS: "darwin", GOARCH: "amd64"
$ java -version (if language is Java)
openjdk version "16.0.2" 2021-07-20
OpenJDK Runtime Environment (build 16.0.2+7-67)
OpenJDK 64-Bit Server VM (build 16.0.2+7-67, mixed mode, sharing)
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.2", GitCommit:"8b5a19147530eaac9476b0ab82980b4088bbc1b2", GitTreeState:"clean", BuildDate:"2021-09-15T21:38:50Z", GoVersion:"go1.16.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean", BuildDate:"2021-01-13T13:20:00Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.22) and server (1.20) exceeds the supported minor version skew of +/-1
Possible Solution
Keep Watch for Deployment events and reconcile if there is any changes in Deployment.
The text was updated successfully, but these errors were encountered:
Bug Report
What did you do?
Followed below steps
--> deployment size is 5
--> 5 pods
--> now changed to 2 pods
--> CR still with size in 5
--> but still stuck in 2
Expected - After deployment changes, it should reconcile and match it with CR
What did you expect to see?
It must reconcile and match Deployment state to CR - User defined state.
What did you see instead? Under which circumstances?
Nothing happened and Cluster contains updated Deployment state.
Environment
Kubernetes cluster type:
Minikube
$ operator-sdk version
openjdk version "16.0.2" 2021-07-20
OpenJDK Runtime Environment (build 16.0.2+7-67)
OpenJDK 64-Bit Server VM (build 16.0.2+7-67, mixed mode, sharing)
laxmikantbhaskarpandhare@lpandhar-mac memcached-quarkus-operator % operator-sdk version
operator-sdk version: "v1.14.0-11-g3d61d762-dirty", commit: "3d61d762ea0ac9926afc0b30042e35f257becad2", kubernetes version: "v1.21", go version: "go1.17.2", GOOS: "darwin", GOARCH: "amd64"
$ java -version
(if language is Java)openjdk version "16.0.2" 2021-07-20
OpenJDK Runtime Environment (build 16.0.2+7-67)
OpenJDK 64-Bit Server VM (build 16.0.2+7-67, mixed mode, sharing)
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.2", GitCommit:"8b5a19147530eaac9476b0ab82980b4088bbc1b2", GitTreeState:"clean", BuildDate:"2021-09-15T21:38:50Z", GoVersion:"go1.16.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean", BuildDate:"2021-01-13T13:20:00Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.22) and server (1.20) exceeds the supported minor version skew of +/-1
Possible Solution
Keep Watch for Deployment events and reconcile if there is any changes in Deployment.
The text was updated successfully, but these errors were encountered: