apache / apache/ozhera

[enhancement] Move the creation of webhook-config to ozhera-operator

Open
#210 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Java
Stars
122
Forks
46
Avg merge
11h 56m
Merged PRs (30d)
9

Description

Currently, the creation of hera-webhook-config is done within the ozhera-webhook-server service. When the ozhera-webhook-server service is terminated, the hera-webhook-config is also destroyed, which is not very elegant. Resources like hera-webhook-config, CSR, etc., only need to be created once and do not need to be frequently created and destroyed.

Additionally, this approach is not very friendly to OzHera's permission convergence.

For details on OzHera's permission convergence, you can refer to this issue: #209

Contributor guide

Open the contributing guide

Research direction

Start by reading the ozhera-webhook-server and ozhera-operator components, then review issue #209 for the permission-convergence context. Identify where hera-webhook-config, CSR, and related resources are created, and verify that they remain after ozhera-webhook-server is terminated while fitting OzHera's permission model.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, kubernetes
Domain
devops, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.