Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adapt fe-docs chart for new operations cluster #4591

Merged
merged 15 commits into from
Feb 15, 2024
Merged

Conversation

marians
Copy link
Member

@marians marians commented Feb 13, 2024

Towards https://github.com/giantswarm/giantswarm/issues/29470

This PR attempts to make the fe-docs chart deployable on k8s 1.25

Included changes:

  • Adds security details to values.yaml which are already applied in the chart
  • Updates schema for values.yaml
  • Adds ci values
  • Sets explicit NGINX configuration for fe-docs
  • Updates nginx-unprivileged to 1.25
  • Sets separate liveness probe path

@marians marians self-assigned this Feb 13, 2024
@marians marians marked this pull request as ready for review February 13, 2024 12:57
@marians marians requested a review from a team as a code owner February 13, 2024 12:57
@marians
Copy link
Member Author

marians commented Feb 14, 2024

FYI: I changed the CircleCI config to publish dev builds for fe-docs, too. Might revert this after testing.

@marians
Copy link
Member Author

marians commented Feb 15, 2024

The app still fails to deploy because of mkdir() "/tmp/proxy_temp" failed (30: Read-only file system). I'll try to remove the need for a cache dir, since fe-docs is all static content anyway.

@marians marians changed the title Fix security spec for fe-docs chart Adapt fe-docs chart for new operations cluster Feb 15, 2024
@marians marians merged commit c91604e into main Feb 15, 2024
18 checks passed
@marians marians deleted the fix-security-spec branch February 15, 2024 13:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants