Skip to content

Conversation

@pleshakov
Copy link
Contributor

Proposed changes

This PR ensures that during the Ingress Controller start, Secret resources are processed before any of the resources that reference those Secrets. This prevents the IC from generating incorrect config and reporting warnings about missing Secrets.

Note that the incorrect config and warnings were temporary and only occurred at the Ingress Controller start before the IC pod was considered ready (passed the readiness probe).

Fixes #1448

Copy link
Contributor

@soneillf5 soneillf5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

This commit ensures that during the Ingress Controller start,
Secret resources are processed before any of the resources that
reference those Secrets. This prevents the IC from generating
incorrect config and reporting warnings about missing Secrets.

Note that the incorrect config and warnings were temporary
and only occurred at the Ingress Controller start before the IC pod
was considered ready (passed the readiness probe).
@pleshakov pleshakov force-pushed the fix-secret-warnings branch from 0b29e10 to b94e8d0 Compare June 10, 2021 17:27
@pleshakov
Copy link
Contributor Author

rebased against master to fix the failing pipeline

@pleshakov pleshakov merged commit 10cb396 into master Jun 15, 2021
@pleshakov pleshakov deleted the fix-secret-warnings branch June 15, 2021 17:17
@pleshakov pleshakov changed the title Fix config and warnings about secrets at IC start Fix incorrect configuration and unexpected warnings about Secrets at the IC start Jun 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug An issue reporting a potential bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Help needed - tls secret took long to discover(ingress version: 1.10, kubernetes version: 1.20)

4 participants