Bug 1924657: Fix metrics ports exposed by operator deployment

[periklis]

Description

This PR provides a small fix in the ClusterServiceVersion deployment manifest for the elasticsearch-operator. The fix provides the correct container ports to expose http and cr metrics as expected by OLM-managed deployments.

/cc @blockloop
/assign @ewolinetz

Links

• Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1924657

[openshift-ci-robot]

@periklis: This pull request references Bugzilla bug 1924657, which is invalid:

• expected the bug to target the "4.6.z" release, but it targets "4.7.0" instead
• expected Bugzilla bug 1924657 to depend on a bug targeting a release in 4.7.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1924657: Fix metrics ports exposed by operator deployment

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/test-infra repository.

[periklis]

/bugzilla refresh

[openshift-ci-robot]

@periklis: This pull request references Bugzilla bug 1924657, which is invalid:

• expected Bugzilla bug 1924657 to depend on a bug targeting a release in 4.7.0 and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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/test-infra repository.

[huikang]

@periklis , should this port be 8080 for the operator container since we upgrade to sdk 1.2?

[periklis]

@periklis , should this port be 8080 for the operator container since we upgrade to sdk 1.2?

You are right for upcoming release branching of master, i.e. 5.0.0. However, in release-4.6 we are still using the old operator-sdk.

[ewolinetz]

@periklis we already have the fix for this covered in 5.0 correct?

[ewolinetz]

/approve

[ewolinetz]

adding valid bug label because we are not producing a 4.7 release in Cluster Logging (we are disconnected from needing to provide this in bugzilla already)

[ewolinetz]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ewolinetz, periklis

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ewolinetz]

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

[openshift-ci-robot]

@periklis: All pull requests linked via external trackers have merged:

• openshift/elasticsearch-operator#652

Bugzilla bug 1924657 has been moved to the MODIFIED state.

In response to this:

Bug 1924657: Fix metrics ports exposed by operator deployment

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/test-infra repository.