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: _docs/deployments/kubernetes/custom-kubectl-commands.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ sub_group: kubernetes
6
6
toc:true
7
7
---
8
8
9
-
Asexplained in[Kubernetes deploymentoptions]({{site.baseurl}}/docs/deployments/kubernetes/deployment-options-to-kubernetes/), Codefresh has built-in functionality for deploying to Kubernetes clusters.
9
+
Asdescribed in[Deploymentoptions for Kubernetes]({{site.baseurl}}/docs/deployments/kubernetes/deployment-options-to-kubernetes/), Codefresh has built-in functionality for deploying to Kubernetes clusters.
10
10
11
11
For maximum flexibility with cluster deployments, you can run your own custom`kubectl` commands in a[freestyle step]({{site.baseurl}}/docs/pipelines/steps/freestyle/).
12
12
[Kubectl](https://kubernetes.io/docs/reference/kubectl/overview/){:target="\_blank"} is the command line interface for managing kubernetes clusters.
@@ -16,7 +16,7 @@ Codefresh automatically sets up your [config context](https://kubernetes.io/docs
16
16
The config context is automatically placed for you at the path of the[variable]({{site.baseurl}}/docs/pipelines/variables/)`$CF_KUBECONFIG_PATH`.
17
17
In the current Codefresh implementation, this expands to`/codefresh/volume/sensitive/.kube/config`, within the[shared step volume]({{site.baseurl}}/docs/pipelines/introduction-to-codefresh-pipelines/#sharing-the-workspace-between-build-steps).
18
18
19
-
When you use custom`kubectl` commands, it is your responsibility to template your manifests using any of the available options. To employ Codefresh for templating, it is better to use the dedicated[cf-deploy-kubernetes step]({{site.baseurl}}/docs/deployments/ci-cd-guides/kubernetes-templating/), which provides simple templating capabilities.
19
+
When you use custom`kubectl` commands, it is your responsibility to template your manifests using any of the available options. To employ Codefresh for templating, it is better to use the dedicated[cf-deploy-kubernetes step]({{site.baseurl}}/docs/ci-cd-guides/kubernetes-templating/), which provides simple templating capabilities.
20
20
21
21
##Using the Codefresh kubectl image
22
22
@@ -169,8 +169,8 @@ steps:
169
169
In the example above, we select one of the clusters in each deployment step, and then apply several Kubernetes manifests that constitute an application.
Copy file name to clipboardExpand all lines: _docs/deployments/kubernetes/deployment-options-to-kubernetes.md
+13-12Lines changed: 13 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,27 +13,27 @@ toc: true
13
13
14
14
Codefresh offers several options when it comes to Kubernetes deployments:
15
15
16
-
1. Codefresh UI for ondemand deployments
17
-
This is the easiest deployment option for Kubernetes. See our[Kubernetes quick start guide]({{site.baseurl}}/docs/getting-started/deployment-to-kubernetes-quick-start-guide/).
16
+
1. Codefresh UI for on-demand deployments
17
+
This is the easiest deployment option for Kubernetes. See our[Kubernetesdeploymentquick start]({{site.baseurl}}/docs/quick-start/ci-quickstart/deploy-to-kubernetes/).
18
18
1. Through a dedicated[deploy step]({{site.baseurl}}/docs/pipelines/steps/deploy/) in a pipeline
19
19
Described in this article.
20
20
1. Through the[cf-deploy-kubernetes step]({{site.baseurl}}/docs/ci-cd-guides/kubernetes-templating/) in a pipeline
21
21
Use this to also perform simple templating on Kubernetes manifests.
22
-
1. Through a[freestyle]({{site.baseurl}}/docs/pipelines/steps/freestyle/) step with[Kustomize](https://kustomize.io){:target="\_blank"}.
22
+
1. Through a[freestyle]({{site.baseurl}}/docs/pipelines/steps/freestyle/) step with[Kustomize](https://kustomize.io){:target="\_blank"}.
23
23
See[Deployment with Kustomize]({{site.baseurl}}/docs/example-catalog/cd-examples/deploy-with-kustomize).
24
-
1. Using a[freestyle]({{site.baseurl}}/docs/codefresh-yaml/steps/freestyle/) step with your own`kubectl` commands
24
+
1. Using a freestyle step with your own`kubectl` commands
25
25
This deployment option gives you great flexibility, but assumes that you know how to work with`kubectl`. See[Custom kubectl commands]({{site.baseurl}}/docs/deployments/kubernetes/custom-kubectl-commands/).
26
26
1. Using Helm as a package manager
27
-
See our[Helm quick start guide]({{site.baseurl}}/docs/quick-start/ci-quickstart/deploy-with-helm/).
27
+
See our[Helmdeployment to Kubernetesquick start]({{site.baseurl}}/docs/quick-start/ci-quickstart/deploy-with-helm/).
28
28
29
29
##Prerequisites
30
30
31
-
* A K8s cluster in Codefresh (see[Connecting a Kubernetes cluster]({{site.baseurl}}/docs/integrations/kubernetes/#connect-a-kubernetes-cluster/)
32
-
* Familiarity with the[Codefresh YAML for pipeline definitions]({{site.baseurl}}/docs/pipelines/what-is-the-codefresh-yaml/), basic[pipeline steps]({{site.baseurl}}/docs/pipelines/steps/), and how to describe them
* A K8s cluster in Codefresh (see[Connecting a Kubernetes cluster]({{site.baseurl}}/docs/integrations/kubernetes/#connect-a-kubernetes-cluster)
32
+
* Familiarity with the[Codefresh YAML for pipeline definitions]({{site.baseurl}}/docs/pipelines/what-is-the-codefresh-yaml/), basic[pipeline steps]({{site.baseurl}}/docs/pipelines/steps/), and how to describe them
Here is a basic Codefresh pipeline scenario to build and push your image toDockerhub registry.
36
+
Here is a basic Codefresh pipeline scenario to build and push your image tothe DockerHub registry.
37
37
38
38
`YAML`
39
39
{% highlight yaml %}
@@ -58,7 +58,7 @@ Using this YAML example, we'll add an additional step to deploy the image in Doc
58
58
59
59
##Describe your deployment
60
60
The following instructions describe how to create a new service in your Kubernetes cluster in order to deploy to it.
61
-
>If you're deploying to an existing service in your Kubernetes cluster, please skip to the[next step]({{site.baseurl}}/docs/getting-started/deployment-to-kubernetes-quick-start-guide/#add-a-deployment-step).
61
+
<!--->If you're deploying to an existing service in your Kubernetes cluster, please skip to the [next step]({{site.baseurl}}/docs/getting-started/deployment-to-kubernetes-quick-start-guide/#add-a-deployment-step).-->
62
62
63
63
64
64
1. Go to the**`Kubernetes`→`Services page`**.
@@ -84,7 +84,8 @@ max-width="60%"
84
84
%}
85
85
86
86
##Add a Deployment step
87
-
So now you have deployed your image manually, which is great. But how to trigger the deployment within your pipeline? For that you will need to add a step of a “Deploy” type to the Codefresh YAML manifest file:
87
+
So now you have deployed your image manually, which is great.
88
+
But, how can you trigger the deployment within your pipeline? For that you will need to add a step of type`Deploy` type to the Codefresh YAML manifest file:
88
89
89
90
`YAML`
90
91
{% highlight yaml %}
@@ -134,7 +135,7 @@ steps:
134
135
{% endraw %}
135
136
{% endhighlight %}
136
137
137
-
You can now run the whole pipeline that builds your application from source to adocker image, pushesitto adocker registry and deploysit to your Kubernetes cluster.
138
+
You can now run the whole pipeline, that builds your application from source to aDocker image, pushesthe imageto aDocker registry, and deploysthe image to your Kubernetes cluster.
138
139
139
140
##Related articles
140
141
[Manage your Kubernetes cluster]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/)
With the graphical dashboard it is very easy to locate problematic services or deploy new ones quickly. If there are clusters that are not accessible to your user you can hide them by enabling the*Hide inaccessible clusters* option at the top right of the window in order to simplify the view.
27
+
With the graphical dashboard, it is very easy to locate problematic services or deploy new ones quickly. If there are clusters that are not accessible to your user, you can hide them by enabling the*Hide inaccessible clusters* option at the top right of the window in order to simplify the view.
28
28
29
29
##Viewing your Kubernetes services
30
30
@@ -44,8 +44,8 @@ You can also switch to a Grid view if you prefer that over the default List view
44
44
45
45
{% include image.html
46
46
lightbox="true"
47
-
file="/images/kubernetes/dashboard/grid-view.png"
48
-
url="/images/kubernetes/dashboard/grid-view.png"
47
+
file="/images/kubernetes/grid-view.png"
48
+
url="/images/kubernetes/grid-view.png"
49
49
alt="Kubernetes Dashboard grid view"
50
50
caption="Kubernetes Dashboard grid view"
51
51
max-width="80%"
@@ -83,7 +83,7 @@ max-width="60%"
83
83
%}
84
84
85
85
86
-
Use the following steps in order to add Image and pull secrets from the[connected Docker Registry]({{site.baseurl}}/docs/docker-registries/external-docker-registries/):
86
+
Use the following steps in order to add Image and pull secrets from the connected Docker Registry:
87
87
* Specify the image name in the format`<DOMAIN>/<ACCOUNT>/<IMAGE>:<TAG>`
88
88
* Provide and image pull secret - this will be done for each namespace
89
89
@@ -158,12 +158,12 @@ Some of the possible options are:
158
158
1. The dedicated[deploy step]({{site.baseurl}}/docs/pipelines/steps/deploy/) in a pipeline.
159
159
1. The[cf-deploy-kubernetes step]({{site.baseurl}}/docs/ci-cd-guides/kubernetes-templating/) in a pipeline. This can also perform simple templating on Kubernetes manifests.
160
160
161
-
See morechoices in the[Deployment optionspage]({{site.baseurl}}/docs/deployments/kubernetes/deployment-options-to-kubernetes/).