Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitde27117

Browse files
committed
Update k8s deployment topics
1 parent58bf054 commitde27117

File tree

3 files changed

+24
-23
lines changed

3 files changed

+24
-23
lines changed

‎_docs/deployments/kubernetes/custom-kubectl-commands.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ sub_group: kubernetes
66
toc:true
77
---
88

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.
1010

1111
For maximum flexibility with cluster deployments, you can run your own custom`kubectl` commands in a[freestyle step]({{site.baseurl}}/docs/pipelines/steps/freestyle/).
1212
[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
1616
The config context is automatically placed for you at the path of the[variable]({{site.baseurl}}/docs/pipelines/variables/)`$CF_KUBECONFIG_PATH`.
1717
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).
1818

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.
2020

2121
##Using the Codefresh kubectl image
2222

@@ -169,8 +169,8 @@ steps:
169169
In the example above, we select one of the clusters in each deployment step, and then apply several Kubernetes manifests that constitute an application.
170170

171171
##Related articles
172-
[Managingyour cluster]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/)
173-
[Accessing a Docker registry]({{site.baseurl}}/docs/ci-cd-guides/access-docker-registry-from-kubernetes/)
172+
[ManagingKubernetes clusters]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/)
173+
[Accessing a Docker registry from cluster]({{site.baseurl}}/docs/ci-cd-guides/access-docker-registry-from-kubernetes/)
174174

175175

176176

‎_docs/deployments/kubernetes/deployment-options-to-kubernetes.md‎

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -13,27 +13,27 @@ toc: true
1313

1414
Codefresh offers several options when it comes to Kubernetes deployments:
1515

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/).
1818
1. Through a dedicated[deploy step]({{site.baseurl}}/docs/pipelines/steps/deploy/) in a pipeline
1919
Described in this article.
2020
1. Through the[cf-deploy-kubernetes step]({{site.baseurl}}/docs/ci-cd-guides/kubernetes-templating/) in a pipeline
2121
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"}.
2323
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
2525
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/).
2626
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/).
2828

2929
##Prerequisites
3030

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
33-
*[Integrate yourDocker registry]({{site.baseurl}}/docs/integrations/docker-registries/)with Codefresh
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
33+
*[Docker registry integration]({{site.baseurl}}/docs/integrations/docker-registries/)in Codefresh
3434

3535
##Build and push your image
36-
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.
3737

3838
`YAML`
3939
{% highlight yaml %}
@@ -58,7 +58,7 @@ Using this YAML example, we'll add an additional step to deploy the image in Doc
5858

5959
##Describe your deployment
6060
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).-->
6262

6363

6464
1. Go to the**`Kubernetes`&#8594;`Services page`**.
@@ -84,7 +84,8 @@ max-width="60%"
8484
%}
8585

8686
##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:
8889

8990
`YAML`
9091
{% highlight yaml %}
@@ -134,7 +135,7 @@ steps:
134135
{% endraw %}
135136
{% endhighlight %}
136137

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.
138139

139140
##Related articles
140141
[Manage your Kubernetes cluster]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/)

‎_docs/deployments/kubernetes/manage-kubernetes.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ caption="Codefresh Kubernetes Dashboard"
2424
max-width="80%"
2525
%}
2626

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.
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.
2828

2929
##Viewing your Kubernetes services
3030

@@ -44,8 +44,8 @@ You can also switch to a Grid view if you prefer that over the default List view
4444

4545
{% include image.html
4646
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"
4949
alt="Kubernetes Dashboard grid view"
5050
caption="Kubernetes Dashboard grid view"
5151
max-width="80%"
@@ -83,7 +83,7 @@ max-width="60%"
8383
%}
8484

8585

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:
8787
* Specify the image name in the format`<DOMAIN>/<ACCOUNT>/<IMAGE>:<TAG>`
8888
* Provide and image pull secret - this will be done for each namespace
8989

@@ -158,12 +158,12 @@ Some of the possible options are:
158158
1. The dedicated[deploy step]({{site.baseurl}}/docs/pipelines/steps/deploy/) in a pipeline.
159159
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.
160160

161-
See morechoices in the[Deployment optionspage]({{site.baseurl}}/docs/deployments/kubernetes/deployment-options-to-kubernetes/).
161+
Read more[Deployment optionsfor Kubernetes]({{site.baseurl}}/docs/deployments/kubernetes/deployment-options-to-kubernetes/).
162162
<!-- will need to change xrefs after porting content-->
163163
##Related articles
164-
[Environment dashboard]({{site.baseurl}}/docs/deployments/kubernetes/environment-dashboard/)
164+
[Environment dashboard]({{site.baseurl}}/docs/deployments/kubernetes/environment-dashboard/)
165165
[Add Config Maps]({{site.baseurl}}/docs/ci-cd-guides/add-config-maps-to-your-namespaces/)
166-
[Kubernetes deployment quick start]({{site.baseurl}}/docs/getting-started/deployment-to-kubernetes-quick-start-guide/)
166+
[Kubernetes deployment quick start]({{site.baseurl}}/docs/quick-start/ci-quickstart/deploy-to-kubernetes/)
167167

168168

169169

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp