-
Notifications
You must be signed in to change notification settings - Fork 23
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
Statefulset is looping for "size -1" number of times #82
Comments
@vigneshp826: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@everettraven sorry for tagging you, but appreciate anyone help here to move forward with my production rollout. |
Type of question
General operator-related help
Question
What did you do?
I have playbook which creates statefulset for every CR creation against my operator (for simplicity, removed all other k8 resource creation stuffs). The playbook is getting executed repeatedly as per the replica size upon the CR creation. For example, when the size of the replica is 3, the playbook is executing 2 times.
Setting "watchDependentResources: False", stops this pattern and executes only one time but it is not a better solution in my use case.
What did you expect to see?
Plays should run only once to avoid wasting resource before reconciliation period kicks in.
What did you see instead? Under which circumstances?
Multiple execution of K8 resource creation based on the status output of each loop.
Environment
Operator type:
/language ansible
$operator-sdk version
operator-sdk version: "v1.31.0", commit: "e67da35ef4fff3e471a208904b2a142b27ae32b1", kubernetes version: "1.26.0", go version: "go1.19.11", GOOS: "linux", GOARCH: "amd64"
$ kubectl version
Client Version: v1.28.1 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.25.4
Additional context
Playbook
The text was updated successfully, but these errors were encountered: