kubenetes deploy knative 1.15

已于 2024-08-13 17:20:54 修改
阅读量1k 收藏 10
点赞数 17
文章标签： kubernetes knative
于 2024-08-13 16:32:30 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/yummaster/article/details/141167001
版权

kubenetes deploy knative 1.15

Official document

https://knative.dev/docs/install/

Download yaml (China internet)

Down below 2 yaml from https://bgithub.xyz/knative/serving/releases/tag/knative-v1.15.0
serving-core.yaml
serving-crds.yaml

Down below 2 yaml from https://bgithub.xyz/knative/eventing/releases/tag/knative-v1.15.0
eventing-core.yaml
eventing-crds.yaml

1. Create namespace

[root@localhost ~]# kubectl create namespace knative-serving
[root@localhost ~]# kubectl create namespace knative-eventing

2. deploy knative-eventing

[root@localhost ~]# kubectl apply -f eventing-crds.yaml
customresourcedefinition.apiextensions.k8s.io/apiserversources.sources.knative.dev created
customresourcedefinition.apiextensions.k8s.io/brokers.eventing.knative.dev created
customresourcedefinition.apiextensions.k8s.io/channels.messaging.knative.dev created
customresourcedefinition.apiextensions.k8s.io/containersources.sources.knative.dev created
customresourcedefinition.apiextensions.k8s.io/eventpolicies.eventing.knative.dev created
customresourcedefinition.apiextensions.k8s.io/eventtypes.eventing.knative.dev created
customresourcedefinition.apiextensions.k8s.io/jobsinks.sinks.knative.dev created
customresourcedefinition.apiextensions.k8s.io/parallels.flows.knative.dev created
customresourcedefinition.apiextensions.k8s.io/pingsources.sources.knative.dev created
customresourcedefinition.apiextensions.k8s.io/sequences.flows.knative.dev created
customresourcedefinition.apiextensions.k8s.io/sinkbindings.sources.knative.dev created
customresourcedefinition.apiextensions.k8s.io/subscriptions.messaging.knative.dev created
customresourcedefinition.apiextensions.k8s.io/triggers.eventing.knative.dev created

3. deploy knative-serving

[root@localhost ~]# kubectl apply -f serving-core.yaml 
Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply
namespace/knative-serving configured
role.rbac.authorization.k8s.io/knative-serving-activator created
clusterrole.rbac.authorization.k8s.io/knative-serving-activator-cluster created
clusterrole.rbac.authorization.k8s.io/knative-serving-aggregated-addressable-resolver created
clusterrole.rbac.authorization.k8s.io/knative-serving-addressable-resolver created
clusterrole.rbac.authorization.k8s.io/knative-serving-namespaced-admin created
clusterrole.rbac.authorization.k8s.io/knative-serving-namespaced-edit created
clusterrole.rbac.authorization.k8s.io/knative-serving-namespaced-view created
clusterrole.rbac.authorization.k8s.io/knative-serving-core created
clusterrole.rbac.authorization.k8s.io/knative-serving-podspecable-binding created
serviceaccount/controller created
clusterrole.rbac.authorization.k8s.io/knative-serving-admin created
clusterrolebinding.rbac.authorization.k8s.io/knative-serving-controller-admin created
clusterrolebinding.rbac.authorization.k8s.io/knative-serving-controller-addressable-resolver created
serviceaccount/activator created
rolebinding.rbac.authorization.k8s.io/knative-serving-activator created
clusterrolebinding.rbac.authorization.k8s.io/knative-serving-activator-cluster created
customresourcedefinition.apiextensions.k8s.io/images.caching.internal.knative.dev created
customresourcedefinition.apiextensions.k8s.io/certificates.networking.internal.knative.dev created
customresourcedefinition.apiextensions.k8s.io/configurations.serving.knative.dev created
customresourcedefinition.apiextensions.k8s.io/clusterdomainclaims.networking.internal.knative.dev created
customresourcedefinition.apiextensions.k8s.io/domainmappings.serving.knative.dev created
customresourcedefinition.apiextensions.k8s.io/ingresses.networking.internal.knative.dev created
customresourcedefinition.apiextensions.k8s.io/metrics.autoscaling.internal.knative.dev created
customresourcedefinition.apiextensions.k8s.io/podautoscalers.autoscaling.internal.knative.dev created
customresourcedefinition.apiextensions.k8s.io/revisions.serving.knative.dev created
customresourcedefinition.apiextensions.k8s.io/routes.serving.knative.dev created
customresourcedefinition.apiextensions.k8s.io/serverlessservices.networking.internal.knative.dev created
customresourcedefinition.apiextensions.k8s.io/services.serving.knative.dev created
configmap/config-autoscaler created
configmap/config-certmanager created
configmap/config-defaults created
configmap/config-deployment created
configmap/config-domain created
configmap/config-features created
configmap/config-gc created
configmap/config-leader-election created
configmap/config-logging created
configmap/config-network created
configmap/config-observability created
configmap/config-tracing created
horizontalpodautoscaler.autoscaling/activator created
poddisruptionbudget.policy/activator-pdb created
deployment.apps/activator created
service/activator-service created
deployment.apps/autoscaler created
service/autoscaler created
deployment.apps/controller created
service/controller created
horizontalpodautoscaler.autoscaling/webhook created
poddisruptionbudget.policy/webhook-pdb created
deployment.apps/webhook created
service/webhook created
validatingwebhookconfiguration.admissionregistration.k8s.io/config.webhook.serving.knative.dev created
mutatingwebhookconfiguration.admissionregistration.k8s.io/webhook.serving.knative.dev created
validatingwebhookconfiguration.admissionregistration.k8s.io/validation.webhook.serving.knative.dev created
secret/webhook-certs created
unable to recognize "serving-core.yaml": no matches for kind "Certificate" in version "networking.internal.knative.dev/v1alpha1"
unable to recognize "serving-core.yaml": no matches for kind "Image" in version "caching.internal.knative.dev/v1alpha1"
[root@localhost ~]# 

[root@localhost ~]# kubectl apply -f serving-crds.yaml
customresourcedefinition.apiextensions.k8s.io/certificates.networking.internal.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/configurations.serving.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/clusterdomainclaims.networking.internal.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/domainmappings.serving.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/ingresses.networking.internal.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/metrics.autoscaling.internal.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/podautoscalers.autoscaling.internal.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/revisions.serving.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/routes.serving.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/serverlessservices.networking.internal.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/services.serving.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/images.caching.internal.knative.dev unchanged
[root@localhost ~]# 

[root@localhost ~]# kubectl apply -f eventing-core.yaml
Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply
namespace/knative-eventing configured
serviceaccount/eventing-controller created
clusterrolebinding.rbac.authorization.k8s.io/eventing-controller created
clusterrolebinding.rbac.authorization.k8s.io/eventing-controller-resolver created
clusterrolebinding.rbac.authorization.k8s.io/eventing-controller-source-observer created
clusterrolebinding.rbac.authorization.k8s.io/eventing-controller-sources-controller created
clusterrolebinding.rbac.authorization.k8s.io/eventing-controller-manipulator created
clusterrolebinding.rbac.authorization.k8s.io/eventing-controller-crossnamespace-subscriber created
serviceaccount/job-sink created
clusterrolebinding.rbac.authorization.k8s.io/knative-eventing-job-sink created
serviceaccount/pingsource-mt-adapter created
clusterrolebinding.rbac.authorization.k8s.io/knative-eventing-pingsource-mt-adapter created
serviceaccount/eventing-webhook created
clusterrolebinding.rbac.authorization.k8s.io/eventing-webhook created
rolebinding.rbac.authorization.k8s.io/eventing-webhook created
clusterrolebinding.rbac.authorization.k8s.io/eventing-webhook-resolver created
clusterrolebinding.rbac.authorization.k8s.io/eventing-webhook-podspecable-binding created
configmap/config-br-default-channel created
configmap/config-br-defaults created
configmap/default-ch-webhook created
configmap/config-ping-defaults created
configmap/config-features created
configmap/config-kreference-mapping created
configmap/config-leader-election created
configmap/config-logging created
configmap/config-observability created
configmap/config-sugar created
configmap/config-tracing created
deployment.apps/eventing-controller created
deployment.apps/job-sink created
service/job-sink created
deployment.apps/pingsource-mt-adapter created
horizontalpodautoscaler.autoscaling/eventing-webhook created
poddisruptionbudget.policy/eventing-webhook created
deployment.apps/eventing-webhook created
service/eventing-webhook created
customresourcedefinition.apiextensions.k8s.io/apiserversources.sources.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/brokers.eventing.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/channels.messaging.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/containersources.sources.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/eventpolicies.eventing.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/eventtypes.eventing.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/jobsinks.sinks.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/parallels.flows.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/pingsources.sources.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/sequences.flows.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/sinkbindings.sources.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/subscriptions.messaging.knative.dev unchanged
customresourcedefinition.apiextensions.k8s.io/triggers.eventing.knative.dev unchanged
clusterrole.rbac.authorization.k8s.io/addressable-resolver created
clusterrole.rbac.authorization.k8s.io/service-addressable-resolver created
clusterrole.rbac.authorization.k8s.io/serving-addressable-resolver created
clusterrole.rbac.authorization.k8s.io/channel-addressable-resolver created
clusterrole.rbac.authorization.k8s.io/broker-addressable-resolver created
clusterrole.rbac.authorization.k8s.io/flows-addressable-resolver created
clusterrole.rbac.authorization.k8s.io/eventing-broker-filter created
clusterrole.rbac.authorization.k8s.io/eventing-broker-ingress created
clusterrole.rbac.authorization.k8s.io/eventing-config-reader created
clusterrole.rbac.authorization.k8s.io/channelable-manipulator created
clusterrole.rbac.authorization.k8s.io/meta-channelable-manipulator created
clusterrole.rbac.authorization.k8s.io/knative-eventing-namespaced-admin created
clusterrole.rbac.authorization.k8s.io/knative-messaging-namespaced-admin created
clusterrole.rbac.authorization.k8s.io/knative-flows-namespaced-admin created
clusterrole.rbac.authorization.k8s.io/knative-sources-namespaced-admin created
clusterrole.rbac.authorization.k8s.io/knative-bindings-namespaced-admin created
clusterrole.rbac.authorization.k8s.io/knative-eventing-namespaced-edit created
clusterrole.rbac.authorization.k8s.io/knative-eventing-namespaced-view created
clusterrole.rbac.authorization.k8s.io/knative-eventing-controller created
clusterrole.rbac.authorization.k8s.io/crossnamespace-subscriber created
clusterrole.rbac.authorization.k8s.io/channel-subscriber created
clusterrole.rbac.authorization.k8s.io/broker-subscriber created
clusterrole.rbac.authorization.k8s.io/knative-eventing-job-sink created
clusterrole.rbac.authorization.k8s.io/knative-eventing-pingsource-mt-adapter created
clusterrole.rbac.authorization.k8s.io/podspecable-binding created
clusterrole.rbac.authorization.k8s.io/builtin-podspecable-binding created
clusterrole.rbac.authorization.k8s.io/source-observer created
clusterrole.rbac.authorization.k8s.io/eventing-sources-source-observer created
clusterrole.rbac.authorization.k8s.io/knative-eventing-sources-controller created
clusterrole.rbac.authorization.k8s.io/knative-eventing-webhook created
role.rbac.authorization.k8s.io/knative-eventing-webhook created
validatingwebhookconfiguration.admissionregistration.k8s.io/config.webhook.eventing.knative.dev created
mutatingwebhookconfiguration.admissionregistration.k8s.io/webhook.eventing.knative.dev created
validatingwebhookconfiguration.admissionregistration.k8s.io/validation.webhook.eventing.knative.dev created
secret/eventing-webhook-certs created
mutatingwebhookconfiguration.admissionregistration.k8s.io/sinkbindings.webhook.sources.knative.dev created
[root@localhost ~]#

4. Verify deployed pods

[root@localhost ~]# kubectl get pods -n knative-eventing
NAME                                   READY   STATUS             RESTARTS        AGE
eventing-controller-767646576b-mjpdr   0/1     CrashLoopBackOff   6 (3m15s ago)   9m9s
eventing-webhook-9cf4d9645-l7sn6       0/1     CrashLoopBackOff   6 (3m10s ago)   9m4s
job-sink-594697d789-5tph7              1/1     Running            3 (8m50s ago)   9m8s
[root@localhost ~]# kubectl get pods -n knative-serving
NAME                          READY   STATUS             RESTARTS         AGE
activator-69644644b5-smczd    0/1     CrashLoopBackOff   10 (2m17s ago)   32m
autoscaler-667b8b6d55-jgrsr   0/1     Running            13 (15s ago)     32m
controller-68c74bcbd4-6pzhx   0/1     CrashLoopBackOff   11 (62s ago)     32m
webhook-5596d9b9d4-zcctq      0/1     CrashLoopBackOff   11 (57s ago)     32m
[root@localhost ~]#

5. Verify deployment

[root@localhost ~]# kubectl get deploy -n knative-serving 
NAME         READY   UP-TO-DATE   AVAILABLE   AGE
activator    0/1     1            0           33m
autoscaler   0/1     1            0           33m
controller   0/1     1            0           33m
webhook      0/1     1            0           33m
[root@localhost ~]# kubectl get deploy -n knative-eventing
NAME                    READY   UP-TO-DATE   AVAILABLE   AGE
eventing-controller     0/1     1            0           10m
eventing-webhook        0/1     1            0           10m
job-sink                1/1     1            1           10m
pingsource-mt-adapter   0/0     0            0           10m
[root@localhost ~]#

6. Check required images

knative-serving
[root@localhost ~]# kubectl get pods -n knative-serving -o jsonpath="{..image}" | tr -s '[[:space:]]' '\n' | sort | uniq -c
      1 gcr.io/knative-releases/knative.dev/serving/cmd/activator@sha256:b6d7d96edd8942d679757249f6aa07373461411104ce7c93309f23fba2884f8f
      1 gcr.io/knative-releases/knative.dev/serving/cmd/autoscaler@sha256:119157d871eb3db5a54944464d9920ad378d35292d4c12fd4a765cd016e24f0f
      1 gcr.io/knative-releases/knative.dev/serving/cmd/controller@sha256:80b9865a585900af6cecead24babe03aa79487e9e6306da1444b04148c21c96f
      1 gcr.io/knative-releases/knative.dev/serving/cmd/webhook@sha256:732d9cdf7f5fa5c6055d26b1aa5aad40e3d74ba9f2cb76a1db0f0e4d072b7cd0
      1 sha256:20d0643849defa124c82ff0bf9f5c3eec9ee4b65fcd477a785c8eb556e4cc3a7
      1 sha256:b75c41f4ebdd1eb0566119018721a2c203c5f98e8efd828482a661e647ea09e5
      1 sha256:c53d553e09965ae64ec90e5bd80c23a82dc786aeb033d4b26394ba59e96b957d
      1 sha256:efe57018e1d57b26e697c1468971ed25de7c9576a0bf38940abc443a009d0e63
[root@localhost ~]#
knative-eventing
[root@localhost ~]# kubectl get pods -n knative-eventing -o jsonpath="{..image}" | tr -s '[[:space:]]' '\n' | sort | uniq -c 
      1 gcr.io/knative-releases/knative.dev/eventing/cmd/controller@sha256:947d8aa3c95451759266b5f728eae7704412c1968b84d6f16c3921851ed83d22
      1 gcr.io/knative-releases/knative.dev/eventing/cmd/jobsink@sha256:ac8ffbcabbc336129093e4e8f8a0cd0000319422c5d0ae246ec8e9a972f095cc
      1 gcr.io/knative-releases/knative.dev/eventing/cmd/webhook@sha256:086fc8a0da40730bbfcc32cb12ebc5c883fe75ff05be1bba54435ef1fdc080ce
      1 sha256:0fab07820426373ff57d5dde1bc42579d7a5f0a9d1742d5c7a8ea6a38158f641
      1 sha256:57c70bb07867fe7cda8e57f8712888fefca543180ea176edf18a982ae860b4d4
      1 sha256:bd5eee4bd497cb5475a275f5301c74ec9b29e1fa48b68e39c2ddcef60b6aee67
[root@localhost ~]#

欢迎使用Markdown编辑器

你好！ 这是你第一次使用 Markdown编辑器 所展示的欢迎页。如果你想学习如何使用Markdown编辑器, 可以仔细阅读这篇文章，了解一下Markdown的基本语法知识。

新的改变

我们对Markdown编辑器进行了一些功能拓展与语法支持，除了标准的Markdown编辑器功能，我们增加了如下几点新功能，帮助你用它写博客：

  1. 全新的界面设计 ，将会带来全新的写作体验；
  2. 在创作中心设置你喜爱的代码高亮样式，Markdown 将代码片显示选择的高亮样式 进行展示；
  3. 增加了 图片拖拽 功能，你可以将本地的图片直接拖拽到编辑区域直接展示；
  4. 全新的 KaTeX数学公式 语法；
  5. 增加了支持甘特图的mermaid语法1 功能；
  6. 增加了 多屏幕编辑 Markdown文章功能；
  7. 增加了 焦点写作模式、预览模式、简洁写作模式、左右区域同步滚轮设置 等功能，功能按钮位于编辑区域与预览区域中间；
  8. 增加了 检查列表 功能。

功能快捷键

撤销：Ctrl/Command + Z
重做：Ctrl/Command + Y
加粗：Ctrl/Command + B
斜体：Ctrl/Command + I
标题：Ctrl/Command + Shift + H
无序列表：Ctrl/Command + Shift + U
有序列表：Ctrl/Command + Shift + O
检查列表：Ctrl/Command + Shift + C
插入代码：Ctrl/Command + Shift + K
插入链接：Ctrl/Command + Shift + L
插入图片：Ctrl/Command + Shift + G
查找：Ctrl/Command + F
替换：Ctrl/Command + G

合理的创建标题，有助于目录的生成

直接输入1次#，并按下space后，将生成1级标题。
输入2次#，并按下space后，将生成2级标题。
以此类推，我们支持6级标题。有助于使用TOC语法后生成一个完美的目录。

如何改变文本的样式

强调文本 强调文本

加粗文本 加粗文本

标记文本

删除文本

引用文本

H2O is是液体。

210 运算结果是 1024.

插入链接与图片

链接: link.

图片: Alt

带尺寸的图片: Alt

居中的图片: Alt

居中并且带尺寸的图片: Alt

当然，我们为了让用户更加便捷，我们增加了图片拖拽功能。

如何插入一段漂亮的代码片

去博客设置页面，选择一款你喜欢的代码片高亮样式，下面展示同样高亮的 代码片.

// An highlighted block
var foo = 'bar';

生成一个适合你的列表

  • 项目
    • 项目
      • 项目
  1. 项目1
  2. 项目2
  3. 项目3
  • 计划任务
  • 完成任务

创建一个表格

一个简单的表格是这么创建的：

项目Value
电脑$1600
手机$12
导管$1

设定内容居中、居左、居右

使用:---------:居中
使用:----------居左
使用----------:居右

第一列第二列第三列
第一列文本居中第二列文本居右第三列文本居左

SmartyPants

SmartyPants将ASCII标点字符转换为“智能”印刷标点HTML实体。例如：

TYPEASCIIHTML
Single backticks'Isn't this fun?'‘Isn’t this fun?’
Quotes"Isn't this fun?"“Isn’t this fun?”
Dashes-- is en-dash, --- is em-dash– is en-dash, — is em-dash

创建一个自定义列表

Markdown
Text-to- HTML conversion tool
Authors
John
Luke

如何创建一个注脚

一个具有注脚的文本。2

注释也是必不可少的

Markdown将文本转换为 HTML。

KaTeX数学公式

您可以使用渲染LaTeX数学表达式 KaTeX:

Gamma公式展示 Γ ( n ) = ( n − 1 ) ! ∀ n ∈ N \Gamma(n) = (n-1)!\quad\forall n\in\mathbb N Γ(n)=(n−1)!∀n∈N 是通过欧拉积分

Γ ( z ) = ∫ 0 ∞ t z − 1 e − t d t   . \Gamma(z) = \int_0^\infty t^{z-1}e^{-t}dt\,. Γ(z)=∫0∞​tz−1e−tdt.

你可以找到更多关于的信息 LaTeX 数学表达式here.

新的甘特图功能，丰富你的文章

2014-01-07 2014-01-09 2014-01-11 2014-01-13 2014-01-15 2014-01-17 2014-01-19 2014-01-21 已完成 进行中 计划一 计划二 现有任务 Adding GANTT diagram functionality to mermaid
  • 关于 甘特图 语法，参考 这儿,

UML 图表

可以使用UML图表进行渲染。 Mermaid. 例如下面产生的一个序列图：

张三 李四 王五 你好！李四, 最近怎么样? 你最近怎么样，王五？ 我很好，谢谢! 我很好，谢谢! 李四想了很长时间, 文字太长了 不适合放在一行. 打量着王五... 很好... 王五, 你怎么样? 张三 李四 王五

这将产生一个流程图。:

链接
长方形
圆
圆角长方形
菱形
  • 关于 Mermaid 语法，参考 这儿,

FLowchart流程图

我们依旧会支持flowchart的流程图：

Created with Raphaël 2.3.0 开始 我的操作 确认？ 结束 yes no
  • 关于 Flowchart流程图 语法，参考 这儿.

导出与导入

导出

如果你想尝试使用此编辑器, 你可以在此篇文章任意编辑。当你完成了一篇文章的写作, 在上方工具栏找到 文章导出 ，生成一个.md文件或者.html文件进行本地保存。

导入

如果你想加载一篇你写过的.md文件，在上方工具栏可以选择导入功能进行对应扩展名的文件导入，
继续你的创作。

  1. mermaid语法说明 ↩︎

  2. 注脚的解释 ↩︎

yummaster
关注
Kubernetes V1.15管理NVIDIA GPU容器
weichuangxxb的博客
10-08 1175
参考链接: nvidia-k8s-device-plugin k8s-1.15调度GPU文档 nvidia-docker 0. GPU主机依赖 1.下载nvidia-driver(官方提示要约等于361.93) 2.安装nvidia-docker2.x(nvidia-docker1.x和2.x完全不同) 3.docker配置成nvidia的默认运行时 4.kubernetes版本大于1....
export kubernetes deploy read.txt
03-27
如何导出 deployment 配置信息: kubectl get deployment -n kube-system deploy-name -o yaml > deploy-name.yaml
publish over ssh、 Kubernetes Continuous Deploy插件
进行中
09-11 673
地址：​​​​​​Publish Over SSH 里面有 各种版本 脚本没有执行，可能是版本不对，我用的1.22的版本不行。换成20的版本就ok了 SSH: Connecting from host [iZ8vb1c8z4pqb2didmikwkZ] SSH: Connecting with configuration [master_server] ... SSH: EXEC: completed after 400 ms SSH: Disconnecting configurati..
knative_使用knative在kubernetes上实现无服务器
weixin_26755331的博客
09-06 640
knativeIf you’re already using Kubernetes, you’ve probably heard about serverless. While both platforms are scalable, serverless goes the extra mile by providing developers with running code without w...
kubeadm安装kubernetes1.15详细步骤
MappleZF的博客
10-09 1556
kubeadm是Kubernetes官方提供的用于快速安装Kubernetes集群的工具。本次使用阿里云的1台master和2台k8s-node进行操作。 1.准备环境-系统配置 1.1 三台主机hosts中添加主机名与IP对应关系： [root@k8s-master:/root]# vim /etc/hosts 1.2关闭防火墙、selinux和swap： systemctl stop fi...
Kubernetes Continuous Deploy插件的使用
m0_67505608的博客
03-16 802
这个插件的这个版本最好使！！！ Kubernetes CD to version 1.0 升级到高级 在使用中会报错 ERROR: ERROR: Can't construct a java object for tag:yaml.org,2002:io.kubernetes.client.openapi.models.V1Deployment; exception=Class not found: io.kubernetes.client.openapi.models.V1Deployme..
Deploy to Kubernetes
BLOG域名:programb.blog.csdn.net
04-22 737
Estimated reading time: 5 minutes Prerequisites Download and install Docker Desktop as described in Orientation and setup. Work through containerizing an application in Part 2. Make sure that Kubernet...
Kubernetes1.15部署Dashboard
06-27 323
=== master节点上进行如下操作 === 部署方法1-原生文件部署： kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v1.10.1/src/deploy/recommended/kubernetes-dashboard.yaml 默认使用端口：8001默认镜像下载地址：google 部署方法2...
python 使用requests调用 kubernetes API创建deploy
weixin_56790951的博客
09-14 741
python 调用k8s api 创建deploy
Kubernetes的deploy、service、namespace模板
jiangbenchu的博客
08-08 1763
deploy.yaml #Deployment apiVersion: extensions/v1beta1 kind: Deployment metadata: name: 003-paas-static-deploy namespace: paas-app-dev2 labels: name: 003-paas-static-deploy spec: ...
Valheim-kubernetes-deploy
03-15
Valheim-kubernetes-部署 来自启发。 将端口公开为节点端口，将Valheim专用游戏服务器部署到Kubernetes。 这就是我用于服务器的内容。 您可能需要对其进行修改以供自己使用。 档案文件 Docker文件 建立Valheim专用...
kubernetes-deploy-go
04-17
流水线示例 这是一个示例golang项目，用于演示与rancher管道的集成。 建造 go build -o ./bin/hello-server 跑步 ./bin/hello-server 执照 版权所有（c）2014-2018 根据Apache许可证2.0版（“许可证”）获得许可...
k8s 修炼手册
最新发布
ljj19910401的博客
09-26 487
svc 添加label ver=4.2 此时svc流量至通向新版本pod 修改为ver=4.1 svc流量则通向旧版本。后创建governing headless Service 无头服务 管理该StatefulSet所有DNS子域名。升级按顺序从索引号最大的Pod开始,每次更新一个,直到最小索引号的Pod。pod label 有ver 这时候新旧版本pod svc都提供服务。首先依照volume章创建StorageClass。部署nfs-client-provisioner。部署StatefulSet。
K8s Calico替换为Cilium,以及安装Cilium过程(鲁莽版)
博然的宝藏库
09-22 519
这将会下载并解压 Cilium 的 Helm Chart 到当前目录下的 `cilium` 文件夹中。### 步骤 3：下载 Cilium Helm Chart 到本地。### 步骤 2：添加 Cilium Helm 仓库。#### 添加 Cilium Helm 仓库。### 步骤 1：安装 Helm。#### 安装 Helm。一、删除Calico。二、下载Cilium。三、安装Cilium。
k8s pv(PersistentVolume) 状态含义
岳来的博客
09-24 311
pv 状态机器相关概念
k8s介绍-搭建k8s
czzwa的博客
09-23 717
应用部署方式演变传统部署：互联网早期，会直接将应用程序部署在物理机上优点：简单，不需要其他技术的参与缺点：不能为应用程序定义资源使用边界，很难合理地分配计算资源，而且程序之间容器产生影响虚拟化部署：可以在一台物理机上运行多个虚拟机，每个虚拟机都是独立的一个环境优点：程序环境不会相互产生影响，提供了一定程度的安全性缺点： 增加了操作系统，浪费了部分资源容器化部署：与虚拟化类似，但是共享了操作系统优点：可以保证每个容器拥有自己的文件系统、CPU、内存、进程空间等。
Sealos 快速创建k8s 集群
李昊轩的博客
09-24 461
Sealos 是一个用于管理 Kubernetes 集群的开源工具。它提供了一种简单、高效的方式来部署、管理和监控 Kubernetes 集群。通过 Sealos，用户可以快速创建和配置 Kubernetes 集群，实现容器化应用的部署和管理。
9.24-k8s服务发布
qq_70752758的博客
09-24 579
本次实战域名服务器为：wp-web.com:30080后续论坛网站自行搭建。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值