Skip to content
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

Change WatcherAPI deployment to a statefulset #59

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

cescgina
Copy link
Contributor

@cescgina cescgina commented Feb 3, 2025

In order to be consistent with the decision engine and applier, use an
statefulset instead of a deployment for watcher-api. This change also
modifies the config templates to ensure we don't rely on the root user
at all, and run using either the watcher or apache users.

Related: OSPRH-13578

@openshift-ci openshift-ci bot requested review from dprince and raukadah February 3, 2025 11:40
Copy link

openshift-ci bot commented Feb 3, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from cescgina. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@cescgina cescgina force-pushed the watcherapi_statefulset branch 2 times, most recently from 7967004 to 526c779 Compare February 3, 2025 12:06
controllers/watcherapi_controller.go Show resolved Hide resolved
pkg/watcherapi/deployment.go Outdated Show resolved Hide resolved
pkg/watcherapi/deployment.go Outdated Show resolved Hide resolved
pkg/watcherapi/deployment.go Show resolved Hide resolved
pkg/watcherapi/deployment.go Show resolved Hide resolved
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 to add a scaling scenario for testing. Thanks!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 thanks for that

In order to be consitent with the decision engine and applier, use an
statefulset instead of a deployment for watcher-api. This change also
modifies the config templates to ensure we don't rely on the root user
at all, and run using either the watcher or apache users.
@cescgina cescgina force-pushed the watcherapi_statefulset branch from 526c779 to cf93871 Compare February 3, 2025 16:27
Copy link
Contributor

@marios marios left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good/didn't spot something and seems consistent with the others

@viroel
Copy link
Contributor

viroel commented Feb 4, 2025

looks good @cescgina

@viroel
Copy link
Contributor

viroel commented Feb 4, 2025

/lgtm

thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants