You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: choose-native-plants/README.md
+16-33Lines changed: 16 additions & 33 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Choose Native Plants Application
2
2
3
-
This README provides instructions for deploying and managing the Choose Native Plants application in the Kubernetes cluster using Helm.
3
+
This README provides instructions for deploying and managing the Choose Native Plants application in the Kubernetes cluster using GitOps.
4
4
5
5
## Creating a New Release
6
6
@@ -24,37 +24,18 @@ git push origin main
24
24
- Go to the [GitHub repository](https://github.com/CodeForPhilly/pa-wildflower-selector)
25
25
- Click on the "Releases" tab
26
26
- Click "Draft a new release"
27
-
- Set the tag version to match your release (e.g., "v2.0.3")
28
-
- Set the release title (e.g., "Choose Native Plants v2.0.3")
27
+
- Set the tag version to match your release (e.g., "v2.0.4")
28
+
- Set the release title (e.g., "Choose Native Plants v2.0.4")
29
29
- Add release notes describing the changes in this version
30
30
- Click "Publish release"
31
31
32
32
4. The GitHub Actions workflow will automatically build and push the new Docker image to the GitHub Container Registry with the specified tag.
33
33
34
-
## Deploying the Application with Helm
34
+
## Deploying the Application to Sandbox
35
35
36
-
Once you've updated the release-values.yaml file and created a GitHub release, you can deploy the application using Helm:
36
+
The sandbox environment uses a GitOps approach for deployments. When you push changes to the main branch of the cfp-sandbox-cluster repository, the deployment will be automatically triggered.
37
37
38
-
```powershell
39
-
# Deploy or upgrade the application using Helm
40
-
# Note: This only updates the deployment in the Kubernetes cluster, not your local repository
**Important**: The `helm upgrade` command only affects your Kubernetes cluster deployment. It doesn't modify any files in your local repository. Make sure you've committed and pushed all changes to GitHub before running this command.
45
-
46
-
### Helm Release Management
47
-
48
-
```powershell
49
-
# View release history
50
-
helm history choose-native-plants -n choose-native-plants
kubectl describe pod $POD_NAME -n choose-native-plants
110
91
```
111
92
112
-
## CI/CD Integration with Helm
93
+
## CI/CD Integration with GitOps
113
94
114
-
To integrate Helm into your CI/CD pipeline, update your deployment scripts to use Helm commands instead of direct kubectl commands. Here's a typical workflow:
95
+
The sandbox environment uses a GitOps approach for deployments. Here's the typical workflow:
115
96
116
97
1.**Update Version**: Update the version in release-values.yaml as part of your CI process
117
-
2.**Commit Changes**: Commit the updated release-values.yaml to your repository
118
-
3.**Deploy with Helm**: Use the helm upgrade command in your deployment pipeline
98
+
2.**Commit Changes**: Commit the updated release-values.yaml to the repository
99
+
3.**Push Changes**: Push to the main branch to trigger the GitOps deployment
119
100
120
101
```powershell
121
-
# Example CI/CD script
122
-
$VERSION="2.0.3" # This would be dynamically set in your CI/CD process
102
+
# Example CI/CD script to update version
103
+
$VERSION="2.0.4" # This would be dynamically set in your CI/CD process
0 commit comments