oracle / oracle/oci-cloud-controller-manager
Missing env var flag for log verbosity level
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Go
- Stars
- 158
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
Is this a BUG REPORT or FEATURE REQUEST?
FEATURE REQUEST
Versions
CCM Version:
0.10.0
Environment:
- Kubernetes version (use
kubectl version):
1.15.6 - OS (e.g. from /etc/os-release):
Oracle Linux Server 7.6 - Kernel (e.g.
uname -a):
4.14.35-1844.1.3.el7uek.x86_64 - Others:
What happened?
As a user, I'd like to be in control of the application's log level via an environment variable.
Particularly for oci-flexvolume-driver.
I'd like to use something like this in my Kubernetes manifests for the Daemonset:
env:
- name: LOG_LEVEL
value: ERROR
What you expected to happen?
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
Contributor guide
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.
Research direction
Start by locating the oci-flexvolume-driver log configuration and the Kubernetes DaemonSet manifest described in the issue. Trace how environment variables are passed to the driver and how the current log level is selected. Done means LOG_LEVEL can be set in the manifest and changes the driver's verbosity as requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100