Gcp migrering #5631
Draft
Gcp migrering #5631
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
ramrock93
approved these changes
Mar 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bakgrunn:
Det er vedtatt at alle applikasjoner som kan flyttes til GCP, skal flyttes til GCP
Løsning:
Migrerer k9-sak-web til GCP.
Blocker:
Denne har jeg testet i dev-gcp, og har funnet ut at den ikke kan merges så lenge autentisering i k9-sak baserer seg på host-header fra frontend i tokenhåndtering. Det fungerer i fss i dag siden begge applikasjoner er i samme cluster og vi går direkte fra k9-sak-web til k9-sak sin docker container. Men når vi flytter k9-sak-web til gcp og k9-sak fremdeles er i fss, så må vi gjennom en reverse proxy på veien og da blir det krøll