Route VCL P2: VarnishVCLPolicy CRD and the GatewayClassParameters gate
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
Research direction
Start by reading the existing VarnishCachePolicy model and policy CRDs, then find the GatewayClassParameters definitions and condition handling. The issue depends on a security decision in #94, so read that decision before making changes. Done means the new CRD is installable, conditions are set, and gateway behavior is unchanged.
Written by the indexing model from the issue text.
Description
Part of #94. Depends on the security decision.
Add the API, set conditions, change no behaviour. Shipping this first lets the API be reviewed on its own.
Work
VarnishVCLPolicyCRD, modelled onVarnishCachePolicy: atargetRefof{group, kind, name, sectionName}accepting Gateway or HTTPRoute, plus a ConfigMap reference and key. Ancestor status, as the other policy CRDs have.GatewayClassParametersadditions: the gate from the security decision, androuteVCL.slotPoolSize.- Status conditions:
Accepted;Invalidfor a bad reference, a namespace that is not permitted, or no slot available;Programmedonce the VCL has compiled and been labelled on every pod.
Done when
The CRD is installable, the operator sets conditions on it, and nothing else about the gateway changes.
Notes
Size M.
- Dominant language
- Go
- Stars
- 16
- Forks
- 3
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 10
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from varnish/gateway
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 5 days
-
beta documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
varnish/gateway#58 · 1 comment ·
Maintainers usually reply within 5 days
-
beta documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
varnish/gateway#52 · 1 comment ·
Maintainers usually reply within 5 days
-
beta enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 5 days
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
varnish/gateway#123 · 1 comment ·
Maintainers usually reply within 5 days
Similar issues
-
Date tests fail when the local date differs from the UTC datePossibly taken @unidoc-alip claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
rossoctl/context-guru#1217 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
router-for-me/CLIProxyAPI#7659 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
netsampler/goflow2#601 ·
Maintainers usually reply within 1 day