k8s-deploy-helper 1.5.2 → 1.6.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +38 -56
- package/bin/cli.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,31 +1,24 @@
|
|
|
1
|
-
|
|
1
|
+
# k8s-deploy-helper 🚀
|
|
2
2
|
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
# It is designed to reduce the learning curve of Kubernetes while still supporting real-world DevOps practices.
|
|
3
|
+
k8s-deploy-helper is a simple and beginner-friendly CLI tool that helps you build Docker images and deploy applications to Kubernetes using a guided and automated workflow.
|
|
4
|
+
It is designed to reduce the learning curve of Kubernetes while still supporting real-world DevOps practices.
|
|
6
5
|
|
|
7
6
|
-----
|
|
8
7
|
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
## Deploying an application to Kubernetes usually involves many manual steps:
|
|
8
|
+
## PROBLEM THIS TOOL SOLVES 🧩
|
|
12
9
|
|
|
10
|
+
### Deploying an application to Kubernetes usually involves many manual steps:
|
|
13
11
|
• Creating and maintaining a Dockerfile
|
|
14
12
|
• Writing Kubernetes YAML files (Deployment, Service, etc.)
|
|
15
13
|
• Understanding kubectl commands
|
|
16
14
|
• Managing Docker registry authentication
|
|
17
15
|
• Debugging unclear or low-level runtime errors
|
|
18
16
|
|
|
19
|
-
# For beginners and even intermediate developers, this process can be confusing, time-consuming, and error-prone.
|
|
20
|
-
|
|
21
|
-
# k8s-deploy-helper removes this complexity by automating these steps and guiding the user through a clear, predictable workflow.
|
|
22
|
-
|
|
23
17
|
-----
|
|
24
18
|
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
## k8s-deploy-helper automates the full deployment process by:
|
|
19
|
+
## WHAT THIS TOOL DOES ⚙️
|
|
28
20
|
|
|
21
|
+
### k8s-deploy-helper automates the full deployment process by:
|
|
29
22
|
• Automatically generating missing Docker and Kubernetes configuration files
|
|
30
23
|
• Building Docker images for your application
|
|
31
24
|
• Supporting local deployments without pushing images to Docker Hub
|
|
@@ -33,86 +26,78 @@
|
|
|
33
26
|
• Applying Kubernetes resources using kubectl
|
|
34
27
|
• Detecting missing setup early and displaying clear, actionable error messages
|
|
35
28
|
|
|
36
|
-
You focus on building your application.
|
|
37
|
-
The tool handles the deployment.
|
|
38
|
-
|
|
39
29
|
-----
|
|
40
30
|
|
|
41
|
-
|
|
31
|
+
## REQUIREMENTS (BEGINNER FRIENDLY) 🛠️
|
|
42
32
|
|
|
43
|
-
|
|
33
|
+
### Minimum setup for local usage:
|
|
44
34
|
• Docker Desktop installed
|
|
45
35
|
• Kubernetes enabled inside Docker Desktop
|
|
46
36
|
|
|
47
|
-
|
|
37
|
+
### Docker Desktop already includes:
|
|
48
38
|
• Docker
|
|
49
39
|
• kubectl
|
|
50
40
|
• A local Kubernetes cluster
|
|
51
41
|
|
|
52
|
-
|
|
53
|
-
kubectl get nodes
|
|
54
|
-
|
|
42
|
+
### To verify Kubernetes is running:
|
|
43
|
+
*** kubectl get nodes ***
|
|
44
|
+
|
|
55
45
|
-----
|
|
56
46
|
|
|
57
|
-
|
|
47
|
+
## INSTALLATION 📦
|
|
58
48
|
|
|
59
|
-
|
|
60
|
-
|
|
49
|
+
### Install the package globally using npm:
|
|
50
|
+
*** npm install -g k8s-deploy-helper ***
|
|
61
51
|
|
|
62
|
-
|
|
63
|
-
k8s-deploy --version
|
|
52
|
+
### Verify the installation:
|
|
53
|
+
*** k8s-deploy --version ***
|
|
64
54
|
|
|
65
55
|
-----
|
|
66
56
|
|
|
67
|
-
|
|
57
|
+
## HOW TO USE (STEP-BY-STEP) ▶️
|
|
68
58
|
|
|
69
59
|
## STEP 1: INITIALIZE THE PROJECT ⭐
|
|
70
60
|
|
|
71
|
-
|
|
72
|
-
k8s-deploy init
|
|
61
|
+
If your project does not already have a Dockerfile or k8s.config.json, run:
|
|
62
|
+
*** k8s-deploy init ***
|
|
73
63
|
|
|
74
|
-
|
|
64
|
+
#### This command will:
|
|
75
65
|
• Create a basic Dockerfile
|
|
76
66
|
• Create a k8s.config.json configuration file
|
|
77
67
|
• Prepare your project for Kubernetes deployment
|
|
78
68
|
|
|
79
|
-
# You can modify these files later to match your application needs.
|
|
80
|
-
|
|
81
69
|
## STEP 2: DEPLOY LOCALLY (RECOMMENDED FOR BEGINNERS) 🧪
|
|
82
70
|
|
|
83
|
-
|
|
84
|
-
k8s-deploy deploy --local
|
|
71
|
+
For first-time users, deploy without using Docker Hub or any container registry:
|
|
72
|
+
*** k8s-deploy deploy --local ***
|
|
85
73
|
|
|
86
|
-
|
|
74
|
+
#### What happens during local deployment:
|
|
87
75
|
• The Docker image is built locally
|
|
88
76
|
• Image push to a registry is skipped
|
|
89
77
|
• Kubernetes uses the local image
|
|
90
78
|
• The application is deployed to the local Kubernetes cluster
|
|
91
79
|
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
## STEP 3: STANDARD DEPLOYMENT (OPTIONAL) 🌐
|
|
80
|
+
## STEP 3: STANDARD DEPLOYMENT 🌐
|
|
95
81
|
|
|
96
|
-
|
|
97
|
-
k8s-deploy deploy
|
|
82
|
+
Once you are comfortable and logged into a container registry, run:
|
|
83
|
+
*** k8s-deploy deploy ***
|
|
98
84
|
|
|
99
|
-
|
|
85
|
+
#### This will:
|
|
100
86
|
• Build the Docker image
|
|
101
87
|
• Push the image to the configured registry
|
|
102
88
|
• Deploy the application to Kubernetes
|
|
103
89
|
|
|
104
90
|
-----
|
|
105
91
|
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
# After running the commands, the following files will exist in your project:
|
|
92
|
+
## FILES CREATED BY THE TOOL 📁
|
|
109
93
|
|
|
94
|
+
### After running the commands, the following files will exist in your project:
|
|
110
95
|
Dockerfile
|
|
111
96
|
k8s.config.json
|
|
112
97
|
deployment.yaml
|
|
113
98
|
service.yaml
|
|
114
99
|
|
|
115
|
-
|
|
100
|
+
### These files can be:
|
|
116
101
|
• Reviewed
|
|
117
102
|
• Modified
|
|
118
103
|
• Committed to Git
|
|
@@ -120,29 +105,26 @@ service.yaml
|
|
|
120
105
|
|
|
121
106
|
-----
|
|
122
107
|
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
# When you run the deploy command, the tool performs the following steps:
|
|
108
|
+
## WHAT HAPPENS INTERNALLY 🔍
|
|
126
109
|
|
|
110
|
+
### When you run the deploy command, the tool performs the following steps:
|
|
127
111
|
• Checks for required files
|
|
128
112
|
• Verifies Docker and Kubernetes availability
|
|
129
113
|
• Builds the Docker image
|
|
130
114
|
• Generates Kubernetes YAML files
|
|
131
115
|
• Applies resources using kubectl
|
|
132
116
|
|
|
133
|
-
# Each step is logged clearly so you can understand what is happening.
|
|
134
|
-
|
|
135
117
|
-----
|
|
136
118
|
|
|
137
|
-
|
|
119
|
+
## WHY THIS TOOL IS VALUABLE ⭐
|
|
138
120
|
|
|
139
|
-
|
|
121
|
+
### Without this tool:
|
|
140
122
|
• You manually write Kubernetes YAML
|
|
141
123
|
• You manage Docker commands yourself
|
|
142
124
|
• You deal with registry authentication issues
|
|
143
125
|
• Kubernetes feels complex and fragile
|
|
144
126
|
|
|
145
|
-
|
|
127
|
+
### With this tool:
|
|
146
128
|
• One-command deployment
|
|
147
129
|
• Beginner-safe defaults
|
|
148
130
|
• Hands-on Kubernetes experience
|
|
@@ -150,5 +132,5 @@ service.yaml
|
|
|
150
132
|
|
|
151
133
|
-----
|
|
152
134
|
|
|
153
|
-
|
|
135
|
+
## AUTHOR 👨💻
|
|
154
136
|
Lokesh Shimpi
|
package/bin/cli.js
CHANGED