openshift / openshift/cluster-openshift-apiserver-operator

4.22 and 5.0: TargetDown: check-endpoints/check-endpoints targets in openshift-apiserver

Open Beginner friendly
#718 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
39
Forks
113
Avg merge
1d 5h
Merged PRs (30d)
12

Description

Since the update to 4.22.0, the following alert has been fired

100% of the check-endpoints/check-endpoints targets in openshift-apiserver namespace have been unreachable for more than 15 minutes. This may be a symptom of network connectivity issues, down nodes, or failures within these components. Assess the health of the infrastructure and nodes running these targets and then contact support.

reason: the networkpolicy allow-apiserver doesn't contain the check-endpoint port, 17698

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the _allow-apiserver network policy and the check-endpoints configuration in the operator repository. Verify how port 17698 is exposed and compare that with the policy's allowed ports. Done means the check-endpoints targets in openshift-apiserver are reachable and the TargetDown alert no longer fires.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
networking
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.