-
Notifications
You must be signed in to change notification settings - Fork 26
Refactor workshop to make deployment simpler #316
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
base: riv25
Are you sure you want to change the base?
Conversation
added @allamand and @hmuthusamy for review as they had a lot of changes as well. |
name: keycloak-config | ||
creationPolicy: Owner | ||
deletionPolicy: Retain | ||
deletionPolicy: Retain |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to keep the secret after the external secret is deleted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was being retained in riv25, so did not change it but if we agree that it should be removed, we can change the deletionPolicy
# tenant: tenant1 | ||
# fleet_member: dev | ||
# #TODO I think this is not used here, but already stored in the secret | ||
# enable_cert_manager: "true" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok so this file is enabled by default now. How we defines the addons to install on spoke cluster ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now generating this file during init. However, enabling the addon comes from spoke cluster secret directly. The values in secret are managed from platform/infra/terraform/hub-config.yaml
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
e6dece5
to
a036abc
Compare
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Lets cleanup once merged
# Backend configuration provided via CLI parameters | ||
backend "s3" { | ||
# bucket and provided via -backend-config | ||
key = "gitlabinfra/terraform.tfstate" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be a var?
# Store both hash and key in a single file to avoid regenerating on each run | ||
locals { | ||
# Update password_expiry for password and key rotation | ||
password_expiry = "2025-12-31" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we make it indefinite post RIV?
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
Signed-off-by: Pankaj Walke <[email protected]>
3bd6381
to
3537375
Compare
Signed-off-by: Pankaj Walke <[email protected]>
Issue #, if available:
N/A
Description of changes:
Overview
This PR introduces a comprehensive refactoring of workshop infrastructure, focusing on improved deployment
automation, enhanced security configurations, and streamlined cluster management.
Key Changes
🏗️ Infrastructure Refactoring
• Separated cluster creation from bootstrap process for better modularity
• Added dedicated cluster deployment scripts (platform/infra/terraform/cluster/)
• Enhanced Terraform configuration with improved locals, variables, and provider management
• Consolidated GitLab infrastructure deployment with dedicated terraform module
🔧 Script Improvements
• Refactored deployment scripts with improved error handling and logging
• Added comprehensive utility functions (scripts/utils.sh, argocd-utils.sh, backstage-utils.sh)
• Enhanced initialization process with 0-init.sh and improved URL generation
🔐 Security & Authentication
• Enhanced Keycloak configuration with improved client management and role assignments
• Improved external secrets management with better secret store configurations
• Added pod identity management with comprehensive IAM role configurations
• Enhanced ArgoCD security with PKCE configuration and improved secret handling
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.