oracle / oracle/oci-cloud-controller-manager

annotations aren't recognized

Open
#402 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
158
Forks
108
PR merge metrics
No merged PRs in 30d

Description

BUG REPORT

Versions

CCM Version: actual (latest)

Environment:

  • Kubernetes version (use kubectl version): 1.25.3
  • OS (e.g. from /etc/os-release): Ubuntu 22.04
  • Kernel (e.g. uname -a): 5.10.16
  • Others:

What happened?

I've read the official documentation and tons of other docs. As I can understand, you are able to configure LB with kube annotations. My annotations are the following:

oci.oraclecloud.com/load-balancer-type: "lb" 
service.beta.kubernetes.io/oci-load-balancer-shape: "flexible"
service.beta.kubernetes.io/oci-load-balancer-shape-flex-min: "10Mbps"
service.beta.kubernetes.io/oci-load-balancer-shape-flex-max: "10Mbps" 

I N-checked it and it's the LoadBalancer's annotations. Indentation and syntax is OK. When I delete or comment out the whole annotation block, then it'll create LB automatically as intended.

What you expected to happen?

To modify the load-balancer with the given parameters.

How to reproduce it (as minimally and precisely as possible)?

Create Loadbalancer Service and apply only those specs.

Contributor guide

Open the contributing guide

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 reproducing the issue with a Kubernetes LoadBalancer Service using the listed OCI annotations on Kubernetes 1.25.3. Trace how the cloud controller processes those annotations and compare that path with a Service that has no annotation block. Done means the specified load-balancer parameters are accepted and applied when the Service is created.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
cloud, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.