lyft / lyft/flinkk8soperator

Operator pod in Pending state

Open
#183 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
581
Forks
153
PR merge metrics
No merged PRs in 30d

Description

I installed the operator in my docker-desktop (macOS Catalina 10.15). The operator pod was in pending state for very long time. I followed the [Quick Guide](https://github.com/lyft/flinkk8soperator/blob/master/docs/quick-start-guide.md), only difference is I didn't set config as prescribed as I do not need an `Ingress`.

Expected - at the end of running `flinkk8soperator.yaml` the operator should start in the `flink-operator` namespace.

What happened is, the operator was in `pending` for very long time.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by comparing the reported Docker Desktop setup with docs/quick-start-guide.md and the flinkk8soperator.yaml deployment. Check the operator pod's pending-state details and Kubernetes configuration; done means identifying the cause and confirming that the operator starts in the flink-operator namespace without requiring an Ingress.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go, kubernetes
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.