[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C49F5B4BF2CHNT4X08XP69":3,"skill-same:01M6C49F5B4BF2CHNT4X08XP69":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":42,"commitSha":43,"skillDirectory":5,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6C49F5B4BF2CHNT4X08XP69","migrating-bitnami-to-bitnami-legacy",null,"This rule book helps you migrate Bitnami Helm charts and container images from the bitnami repository to the bitnamilegacy repository.\n\nThis migration is necessary due to Bitnami's transition, effective August 28th, 2025, where existing images will be moved to the legacy repo","stakpak\u002Fcommunity-paks","stakpak","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F86326525?v=4","01M6C48005ADA10YG0BQQX0J4Q","Stakpak","01M6C4804JD6KKZR9AQ9TYS0BT",4,"MIT","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fmigrating-bitnami-to-bitnami-legacy\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31],"migrating bitnami to bitnami legacy","container images","dev","repository","Charts","helm","team","migrate","repo","container","bitnami","bitnami-legacy","bitnami-helm-charts","2026-11-10 10:12:30",false,"---\nname: migrating-bitnami-to-bitnami-legacy\ndescription: |\n  This rule book helps you migrate Bitnami Helm charts and container images from the bitnami repository to the bitnamilegacy repository.\n\n  This migration is necessary due to Bitnami's transition, effective August 28th, 2025, where existing images will be moved to the legacy repo\nlicense: MIT\ntags:\n  - bitnami\n  - bitnami-legacy\n  - bitnami-helm-charts\nmetadata:\n  author: Stakpak \u003Cteam@stakpak.dev>\n  version: \"1.0.2\"\n---\n\n# Bitnami to Bitnami Legacy Migration Rule Book\n\n## 1. Overview\n\nThis rule book provides a systematic approach for migrating **Bitnami Helm charts** and **container images** from the `bitnami` repository to the `bitnamilegacy` repository.\\\nThis migration is necessary due to Bitnami's transition effective **August 28th, 2025**, where existing images will be moved to the legacy repository.\n\n***\n\n## 2. Background\n\n* **Effective Date:** August 28th, 2025\n* **Impact:** All existing Bitnami container images will be moved from `docker.io\u002Fbitnami` to `docker.io\u002Fbitnamilegacy`.\n* **Helm Charts:** Will continue to work but require image repository updates.\n* **Legacy Repository:** Receives no further updates and should only be used as a **temporary migration step**.\n\n***\n\n## 3. Migration Prerequisites\n\n* Access to Kubernetes clusters (staging, sandbox, production).\n* Terraform access with appropriate permissions.\n* Helm CLI installed and configured.\n* kubectl access to target clusters.\n* Communication with stakeholders regarding downtime or risks.\n\n***\n\n## 4. Migration Process\n\n### Phase 1: Discovery and Assessment\n\n1. **Identify Bitnami Charts**\n   ```bash\n   helm list -A\n   helm repo list | grep bitnami\n   ```\n2. **Inventory Current Deployments**\n   * Chart names and versions\n   * Namespaces\n   * Current status\n   * Dependencies\n3. **Check Terraform Configuration**\n   ```bash\n   find . -name \"*.tf\" -exec grep -l \"bitnami\" {} \\;\n   grep -r \"bitnami\" .\u002Fterraform\u002F --include=\"*.tf\" -n\n   ```\n\n### Phase 2: Planning\n\n1. **Create Migration Plan**\\\n   For each identified component:\n   * Current chart version\n   * Target migration approach (image override vs. chart upgrade)\n   * Dependencies and order of operations\n   * Rollback procedures\n\n2. **Chart Verification**\\\n   Before migration, verify that the chart exists in the **Bitnami Legacy** repository:\n   ```bash\n   helm search repo bitnamilegacy\u002F\u003Cchart-name>\n   ```\n   If the chart does not exist, do not proceed and raise an issue with the DevOps team.\n\n### Phase 3: Implementation\n\n1. **Terraform Configuration Updates**\n   * Update image references from `bitnami` → `bitnamilegacy`.\n   * If required, allow insecure images:\n     ```yaml\n     global:\n       security:\n         allowInsecureImages: true\n     ```\n\n2. **Handle StatefulSet Restrictions**\\\n   StatefulSets restrict updates on certain fields.\\\n   If you encounter errors such as:\n   ```\n   updates to statefulset spec for fields other than 'replicas'... are forbidden\n   ```\n   Solution: uninstall and reinstall the Helm chart, then reapply Terraform.\n\n3. **Terraform Execution Steps**\n   ```bash\n   cd terraform && terraform fmt -recursive\n   cd terraform\u002Fenvironments\u002F\u003Cenvironment>\u002F20_platform\n   terraform init\n   terraform plan\n   terraform apply -auto-approve\n   ```\n\n### Phase 4: Validation\n\n1. **Verify Helm Deployments**\n   ```bash\n   helm list -A\n   kubectl get all -n \u003Cnamespace>\n   ```\n2. **Functional Testing**\n   * Verify application integrations\n   * Monitor logs for errors\n3. **Image Verification**\n   ```bash\n   kubectl describe pod \u003Cpod-name> -n \u003Cnamespace> | grep Image\n   ```\n\n### Phase 5: Documentation and Cleanup\n\n1. **Update Documentation**\n   * Record migration completion dates\n   * Update deployment documentation\n   * Note configuration changes\n2. **Monitor Post-Migration**\n   * Monitor for 24–48 hours\n   * Check for performance issues\n   * Validate image pulls\n\n***\n\n## 5. Common Issues and Solutions\n\n* **Issue 1: StatefulSet Update Restrictions**\\\n  *Symptom:* Cannot update StatefulSet spec fields.\\\n  *Solution:* Uninstall and reinstall chart, then reapply configuration.\n\n* **Issue 2: Image Pull Errors**\\\n  *Symptom:* Pods fail with image pull errors.\\\n  *Solution:* Verify `allowInsecureImages: true` is set globally.\n\n* **Issue 3: Configuration Drift**\\\n  *Symptom:* Terraform shows unexpected changes.\\\n  *Solution:* Run `terraform fmt -recursive` and confirm all overrides are correct.\n\n***\n\n## 6. Security Considerations\n\n* `allowInsecureImages` is required for Bitnami Legacy but should be monitored.\n* Implement image vulnerability scanning.\n* Plan for migration away from Legacy images long-term.\n\n***\n\n## 7. Rollback Procedures\n\n* **Immediate Rollback:** Revert Terraform configuration to the previous version.\n* **Helm Rollback:**\n  ```bash\n  helm rollback \u003Crelease> \u003Crevision> -n \u003Cnamespace>\n  ```\n* **Emergency:** Switch back to `bitnami` repository (if still available).\n\n***\n\n## 8. Timeline Recommendations\n\n* **Pre-August 28th, 2025:** Complete staging and sandbox migrations.\n* **August 28th, 2025:** Execute production migration.\n* **Post-Migration:** Monitor for one week, then plan a long-term strategy.\n\n***\n\n## 9. Long-term Strategy\n\nSince the **Bitnami Legacy repository is temporary**, consider:\n\n* Bitnami Secure Images for supported production workloads.\n* Alternative chart providers.\n* Building and maintaining your own container images.\n\n***\n\n## 10. Migration Checklist\n\n### Pre-Migration\n\n* [ ] Inventory all Bitnami deployments\n* [ ] Document current versions and configurations\n* [ ] Test migration process in staging\n* [ ] Prepare rollback procedures\n\n### Migration Execution\n\n* [ ] Update Terraform configurations\n* [ ] Apply changes to staging environment\n* [ ] Validate staging deployment\n* [ ] Apply to sandbox, validate deployment\n* [ ] Apply to production, validate deployment\n\n### Post-Migration\n\n* [ ] Verify all services are functional\n* [ ] Monitor for 24–48 hours\n* [ ] Update documentation\n* [ ] Define long-term strategy\n","# Bitnami to Bitnami Legacy Migration Rule Book\n\n## 1. Overview\n\nThis rule book provides a systematic approach for migrating **Bitnami Helm charts** and **container images** from the `bitnami` repository to the `bitnamilegacy` repository.\\\nThis migration is necessary due to Bitnami's transition effective **August 28th, 2025**, where existing images will be moved to the legacy repository.\n\n***\n\n## 2. Background\n\n* **Effective Date:** August 28th, 2025\n* **Impact:** All existing Bitnami container images will be moved from `docker.io\u002Fbitnami` to `docker.io\u002Fbitnamilegacy`.\n* **Helm Charts:** Will continue to work but require image repository updates.\n* **Legacy Repository:** Receives no further updates and should only be used as a **temporary migration step**.\n\n***\n\n## 3. Migration Prerequisites\n\n* Access to Kubernetes clusters (staging, sandbox, production).\n* Terraform access with appropriate permissions.\n* Helm CLI installed and configured.\n* kubectl access to target clusters.\n* Communication with stakeholders regarding downtime or risks.\n\n***\n\n## 4. Migration Process\n\n### Phase 1: Discovery and Assessment\n\n1. **Identify Bitnami Charts**\n   ```bash\n   helm list -A\n   helm repo list | grep bitnami\n   ```\n2. **Inventory Current Deployments**\n   * Chart names and versions\n   * Namespaces\n   * Current status\n   * Dependencies\n3. **Check Terraform Configuration**\n   ```bash\n   find . -name \"*.tf\" -exec grep -l \"bitnami\" {} \\;\n   grep -r \"bitnami\" .\u002Fterraform\u002F --include=\"*.tf\" -n\n   ```\n\n### Phase 2: Planning\n\n1. **Create Migration Plan**\\\n   For each identified component:\n   * Current chart version\n   * Target migration approach (image override vs. chart upgrade)\n   * Dependencies and order of operations\n   * Rollback procedures\n\n2. **Chart Verification**\\\n   Before migration, verify that the chart exists in the **Bitnami Legacy** repository:\n   ```bash\n   helm search repo bitnamilegacy\u002F\u003Cchart-name>\n   ```\n   If the chart does not exist, do not proceed and raise an issue with the DevOps team.\n\n### Phase 3: Implementation\n\n1. **Terraform Configuration Updates**\n   * Update image references from `bitnami` → `bitnamilegacy`.\n   * If required, allow insecure images:\n     ```yaml\n     global:\n       security:\n         allowInsecureImages: true\n     ```\n\n2. **Handle StatefulSet Restrictions**\\\n   StatefulSets restrict updates on certain fields.\\\n   If you encounter errors such as:\n   ```\n   updates to statefulset spec for fields other than 'replicas'... are forbidden\n   ```\n   Solution: uninstall and reinstall the Helm chart, then reapply Terraform.\n\n3. **Terraform Execution Steps**\n   ```bash\n   cd terraform && terraform fmt -recursive\n   cd terraform\u002Fenvironments\u002F\u003Cenvironment>\u002F20_platform\n   terraform init\n   terraform plan\n   terraform apply -auto-approve\n   ```\n\n### Phase 4: Validation\n\n1. **Verify Helm Deployments**\n   ```bash\n   helm list -A\n   kubectl get all -n \u003Cnamespace>\n   ```\n2. **Functional Testing**\n   * Verify application integrations\n   * Monitor logs for errors\n3. **Image Verification**\n   ```bash\n   kubectl describe pod \u003Cpod-name> -n \u003Cnamespace> | grep Image\n   ```\n\n### Phase 5: Documentation and Cleanup\n\n1. **Update Documentation**\n   * Record migration completion dates\n   * Update deployment documentation\n   * Note configuration changes\n2. **Monitor Post-Migration**\n   * Monitor for 24–48 hours\n   * Check for performance issues\n   * Validate image pulls\n\n***\n\n## 5. Common Issues and Solutions\n\n* **Issue 1: StatefulSet Update Restrictions**\\\n  *Symptom:* Cannot update StatefulSet spec fields.\\\n  *Solution:* Uninstall and reinstall chart, then reapply configuration.\n\n* **Issue 2: Image Pull Errors**\\\n  *Symptom:* Pods fail with image pull errors.\\\n  *Solution:* Verify `allowInsecureImages: true` is set globally.\n\n* **Issue 3: Configuration Drift**\\\n  *Symptom:* Terraform shows unexpected changes.\\\n  *Solution:* Run `terraform fmt -recursive` and confirm all overrides are correct.\n\n***\n\n## 6. Security Considerations\n\n* `allowInsecureImages` is required for Bitnami Legacy but should be monitored.\n* Implement image vulnerability scanning.\n* Plan for migration away from Legacy images long-term.\n\n***\n\n## 7. Rollback Procedures\n\n* **Immediate Rollback:** Revert Terraform configuration to the previous version.\n* **Helm Rollback:**\n  ```bash\n  helm rollback \u003Crelease> \u003Crevision> -n \u003Cnamespace>\n  ```\n* **Emergency:** Switch back to `bitnami` repository (if still available).\n\n***\n\n## 8. Timeline Recommendations\n\n* **Pre-August 28th, 2025:** Complete staging and sandbox migrations.\n* **August 28th, 2025:** Execute production migration.\n* **Post-Migration:** Monitor for one week, then plan a long-term strategy.\n\n***\n\n## 9. Long-term Strategy\n\nSince the **Bitnami Legacy repository is temporary**, consider:\n\n* Bitnami Secure Images for supported production workloads.\n* Alternative chart providers.\n* Building and maintaining your own container images.\n\n***\n\n## 10. Migration Checklist\n\n### Pre-Migration\n\n* [ ] Inventory all Bitnami deployments\n* [ ] Document current versions and configurations\n* [ ] Test migration process in staging\n* [ ] Prepare rollback procedures\n\n### Migration Execution\n\n* [ ] Update Terraform configurations\n* [ ] Apply changes to staging environment\n* [ ] Validate staging deployment\n* [ ] Apply to sandbox, validate deployment\n* [ ] Apply to production, validate deployment\n\n### Post-Migration\n\n* [ ] Verify all services are functional\n* [ ] Monitor for 24–48 hours\n* [ ] Update documentation\n* [ ] Define long-term strategy\n",{"name":5,"tags":37,"license":15,"metadata":38,"description":41},[29,30,31],{"author":39,"version":40},"Stakpak \u003Cteam@stakpak.dev>","1.0.2","This rule book helps you migrate Bitnami Helm charts and container images from the bitnami repository to the bitnamilegacy repository.\n\nThis migration is necessary due to Bitnami's transition, effective August 28th, 2025, where existing images will be moved to the legacy repo\n","main","d9bbde9885439c55adad930456b2660b0c37c052",1,"https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks","https:\u002F\u002Fgithub.com\u002Fstakpak","https:\u002F\u002Fwww.stakpak.dev","AI that runs your Infra","2026-07-04 20:18:32",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add stakpak\u002Fcommunity-paks --skill migrating-bitnami-to-bitnami-legacy",{"tool":56,"command":57},"bunx","bunx skills add stakpak\u002Fcommunity-paks --skill migrating-bitnami-to-bitnami-legacy",{"tool":59,"command":60},"pnpm","pnpm dlx skills add stakpak\u002Fcommunity-paks --skill migrating-bitnami-to-bitnami-legacy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fmigrating-bitnami-to-bitnami-legacy\u002FSKILL.md",true,[64,70],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fapi_documentation.md","REFERENCE","参考文档",12592,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-obtain-coupons-all-in-one\u002Freferences\u002Fapi_documentation.md",{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"scripts\u002Ffetch_coupons.py","SCRIPT","脚本",18878,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-obtain-coupons-all-in-one\u002Fscripts\u002Ffetch_coupons.py",[77,114,138,156,176,187],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":96,"publishedAt":32},"01M6C49TTAVC8Q9CTTC05F6VSR","vllm-deployment","Deploy vLLM for high-performance LLM inference. Covers Docker CPU\u002FGPU deployments and cloud VM provisioning with OpenAI-compatible API endpoints.","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fvllm-deployment\u002FSKILL.md",[83,88,91],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[97,98,99,100,101,102,103,104,25,105,106,107,108,109,110,111,21,112,113],"vllm deployment","vLLM","deployment","docker","performance","openai-api","llm inference","learning","api","provisioning","machine-learning","inference","cloud","gpu","openai","vm","deploy",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":121,"publishedAt":32},"01M6C49R31XN7KJ7Y0Y78XVYTQ","terrateam-usage-guide","A comprehensive guide for configuring and using Terrateam, an open-source GitOps CI\u002FCD platform for Terraform and OpenTofu. Covers configuration file structure, access control, workflows, OIDC authentication, drift detection, and best practices for managing infrastructure through pull requests.","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fterrateam-usage-guide\u002FSKILL.md",[120],{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},[122,123,124,125,126,25,127,128,129,130,131,21,132,133,134,135,136,137],"terrateam usage guide","guide","file","opentofu","access","open","detection","oidc","ci","pull","terraform","best practices","authentication","infrastructure","workflows","pull requests",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":32},"01M6C49N78AMM570EGPDXEZZDY","simple-deployment-on-vm","How to do simple but secure deployments using virtual machines on different cloud providers","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fsimple-deployment-on-vm\u002FSKILL.md",[],[145,112,99,146,147,148,149,150,25,151,152,153,154,109,21,155,113],"simple deployment on vm","security","aws","tls configuration","virtual","how","ec2","Providers","tls","dns","secure",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":32},"01M6C49J8PRVT623JWRTTKFNJV","nextjs-on-aws","This document compares various AWS deployment options for Next.js applications, analyzing costs, benefits, limitations, and providing recommendations based on different use cases.","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fnextjs-on-aws\u002FSKILL.md",[],[163,147,164,165,166,167,168,169,170,171,25,172,173,174,21,99,175],"nextjs on aws","nextjs","Next.js","migration","cost-analysis","cost","use","aws deployment","js","analysis","applications","analyzing","architecture",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":32},"01M6C49CHCPGZZ42P5W1MTV3WS","k3s-backup","Backup and recovery solution for K3s clusters. Includes scheduled, pre-shutdown, and manual backup strategies with recovery procedures.","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fk3s-backup\u002FSKILL.md",[],[183,184,185,21,186,25],"k3s backup","k3s","backup","recovery",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":193,"publishedAt":32},"01M6C49ANM9YZQRP7FQPEKCPBS","infrastructure-software-upgrades","Generic guidelines on how to perform infrastructure component upgrades in a reliable way","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Finfrastructure-software-upgrades\u002FSKILL.md",[],[135,194,195,25,150,196,197,21,198,199,200],"upgrades","infrastructure software upgrades","guidelines","component","maintenance","operations","devops"]