Ingress 的资源帮助信息介绍

  1. [root@master ~]# kubectl explain ingress
  2. KIND: Ingress
  3. VERSION: extensions/v1beta1
  4.  
  5. DESCRIPTION:
  6. Ingress is a collection of rules that allow inbound connections to reach
  7. the endpoints defined by a backend. An Ingress can be configured to give
  8. services externally-reachable urls, load balance traffic, terminate SSL,
  9. offer name based virtual hosting etc. DEPRECATED - This group version of
  10. Ingress is deprecated by networking.k8s.io/v1beta1 Ingress. See the release
  11. notes for more information.
  12.  
  13. FIELDS:
  14. apiVersion <string>
  15. APIVersion defines the versioned schema of this representation of an
  16. object. Servers should convert recognized schemas to the latest internal
  17. value, and may reject unrecognized values. More info:
  18. https://git.k8s.io/community/contributors/devel/api-conventions.md#resources
  19.  
  20. kind <string>
  21. Kind is a string value representing the REST resource this object
  22. represents. Servers may infer this from the endpoint the client submits
  23. requests to. Cannot be updated. In CamelCase. More info:
  24. https://git.k8s.io/community/contributors/devel/api-conventions.md#types-kinds
  25.  
  26. metadata <Object> 元数据
  27. Standard object's metadata. More info:
  28. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
  29.  
  30. spec <Object> 期望状态
  31. Spec is the desired state of the Ingress. More info:
  32. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
  33.  
  34. status <Object>
  35. Status is the current state of the Ingress. More info:
  36. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

  查看期望状态的帮助信息

  1. [root@master ~]# kubectl explain ingress.spec
  2. KIND: Ingress
  3. VERSION: extensions/v1beta1
  4.  
  5. RESOURCE: spec <Object>
  6.  
  7. DESCRIPTION:
  8. Spec is the desired state of the Ingress. More info:
  9. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
  10.  
  11. IngressSpec describes the Ingress the user wishes to exist.
  12.  
  13. FIELDS:
  14. backend <Object> 后端的pod
  15. A default backend capable of servicing requests that don't match any rule.
  16. At least one of 'backend' or 'rules' must be specified. This field is
  17. optional to allow the loadbalancer controller or defaulting logic to
  18. specify a global default.
  19.  
  20. rules <[]Object> 规则
  21. A list of host rules used to configure the Ingress. If unspecified, or no
  22. rule matches, all traffic is sent to the default backend.
  23.  
  24. tls <[]Object>
  25. TLS configuration. Currently the Ingress only supports a single TLS port,
  26. 443. If multiple members of this list specify different hosts, they will be
  27. multiplexed on the same port according to the hostname specified through
  28. the SNI TLS extension, if the ingress controller fulfilling the ingress
  29. supports SNI.

调度的规则

 

  1. [root@master ~]# kubectl explain ingress.spec.rules
  2. KIND: Ingress
  3. VERSION: extensions/v1beta1
  4.  
  5. RESOURCE: rules <[]Object>
  6.  
  7. DESCRIPTION:
  8. A list of host rules used to configure the Ingress. If unspecified, or no
  9. rule matches, all traffic is sent to the default backend.
  10.  
  11. IngressRule represents the rules mapping the paths under a specified host
  12. to the related backend services. Incoming requests are first evaluated for
  13. a host match, then routed to the backend associated with the matching
  14. IngressRuleValue.
  15.  
  16. FIELDS:
  17. host <string> 主机名
  18. Host is the fully qualified domain name of a network host, as defined by
  19. RFC 3986. Note the following deviations from the "host" part of the URI as
  20. defined in the RFC: 1. IPs are not allowed. Currently an IngressRuleValue
  21. can only apply to the IP in the Spec of the parent Ingress. 2. The `:`
  22. delimiter is not respected because ports are not allowed. Currently the
  23. port of an Ingress is implicitly :80 for http and :443 for https. Both
  24. these may change in the future. Incoming requests are matched against the
  25. host before the IngressRuleValue. If the host is unspecified, the Ingress
  26. routes all traffic based on the specified IngressRuleValue.
  27.  
  28. http <Object> url

  基于主机名匹配

  1. [root@master ~]# kubectl explain ingress.spec.rules.host
  2. KIND: Ingress
  3. VERSION: extensions/v1beta1
  4.  
  5. FIELD: host <string>
  6.  
  7. DESCRIPTION:
  8. Host is the fully qualified domain name of a network host, as defined by
  9. RFC 3986. Note the following deviations from the "host" part of the URI as
  10. defined in the RFC: 1. IPs are not allowed. Currently an IngressRuleValue
  11. can only apply to the IP in the Spec of the parent Ingress. 2. The `:`
  12. delimiter is not respected because ports are not allowed. Currently the
  13. port of an Ingress is implicitly :80 for http and :443 for https. Both
  14. these may change in the future. Incoming requests are matched against the
  15. host before the IngressRuleValue. If the host is unspecified, the Ingress
  16. routes all traffic based on the specified IngressRuleValue.

  url匹配

  1. [root@master ~]# kubectl explain ingress.spec.rules.http
  2. KIND: Ingress
  3. VERSION: extensions/v1beta1
  4.  
  5. RESOURCE: http <Object>
  6.  
  7. DESCRIPTION:
  8.  
  9. HTTPIngressRuleValue is a list of http selectors pointing to backends. In
  10. the example: http://<host>/<path>?<searchpart> -> backend where where parts
  11. of the url correspond to RFC 3986, this resource will be used to match
  12. against everything after the last '/' and before the first '?' or '#'.
  13.  
  14. FIELDS:
  15. paths <[]Object> -required-
  16. A collection of paths that map requests to backends.

  

 

后端pod的帮助信息

  1. KIND: Ingress
  2. VERSION: extensions/v1beta1
  3.  
  4. RESOURCE: backend <Object>
  5.  
  6. DESCRIPTION:
  7. A default backend capable of servicing requests that don't match any rule.
  8. At least one of 'backend' or 'rules' must be specified. This field is
  9. optional to allow the loadbalancer controller or defaulting logic to
  10. specify a global default.
  11.  
  12. IngressBackend describes all endpoints for a given service and port.
  13.  
  14. FIELDS:
  15. serviceName <string> -required- 后端server的名字的定义
  16. Specifies the name of the referenced service.
  17.  
  18. servicePort <string> -required- 端口
  19. Specifies the port of the referenced service.

kubernetes的Ingress资源介绍的更多相关文章

  1. Kubernetes的service资源介绍

    service 三种工作模式:userspace.iptables.ipvs 删除手动创建的service [root@master ~]# kubectl delete svc redis serv ...

  2. Kubernetes 使用 ingress 配置 https 集群(十五)

    目录 一.背景 1.1 需求 1.2 Ingress 1.3 环境介绍 二.安装部署 2.1.创建后端 Pod 应用 2.2 创建后端 Pod Service 2.3.创建 ingress 资源 2. ...

  3. Kubernetes:Ingress总结(一)

    Blog:博客园 个人 参考:Ingress | Kubernetes.<Kubernetes进阶实战>.<Kubernetes网络权威指南 > 何谓Ingress?从字面意思 ...

  4. (八)Kubernetes Ingress资源

    前言 Kubernetes提供了两种内建的云端负载均衡机制(cloud load balancing)用于发布公共应用,一种是工作于传输层的Service资源,它实现的是“TCP负载均衡器”,另一种是 ...

  5. 【转】Kubernetes的Ingress控制器比较

    Kubernetes的Ingress控制器比较 fiisio Kubernetes/云计算/资源调度/Go语言 21 人赞同了该文章 翻译:https://medium.com/flant-com/c ...

  6. 干货分享:如何使用Kubernetes的Ingress API

    您可以通过使用诸如Kong for Kubernetes的Ingress控制器(使用自定义资源定义并提供许多插件)来极大地扩展Ingress资源的功能. Kubernetes正在整个技术行业中得到采用 ...

  7. Kubernetes之Ingress

    在Service篇里面介绍了像集群外部的客户端公开服务的两种方法,还有另一种方法---创建Ingress资源. 定义Ingress (名词)-进入或进入的行为;进入的权利;进入的手段或地点;入口. 接 ...

  8. kubernetes nginx ingress 使用记录

    前言 ingress是一种可以暴露k8s集群内部service的方式,用户编辑配置文件定义一个ingress资源即可实现外部网络访问内网service. ingress controller是来管理所 ...

  9. Kubernetes系列之Helm介绍篇

    本次系列使用的所需部署包版本都使用的目前最新的或最新稳定版,安装包地址请到公众号内回复[K8s实战]获取 介绍 Helm 是 Deis 开发的一个用于 Kubernetes 应用的包管理工具,主要用来 ...

随机推荐

  1. JAVA变量声明在循环体内还是循环体外

    (1) for (int i = 0; i < 10000; ++i) { Object obj = new Object(); System.out.println("obj= &q ...

  2. 1.什么是springboot

    什么是spring? Spring是一个开源框架,2003 年兴起的一个轻量级的Java 开发框架,作者:Rod Johnson . Spring是为了解决企业级应用开发的复杂性而创建的,简化开发. ...

  3. [AGC027C]ABland Yard

    Description AGC027C 给定一张图,点有标号A或B,计算是否对于任意的一个由AB构成的字符串都在图中有对应的路径. Solution 观察可以发现,如果有个环(不一定是简单环)是AAB ...

  4. 【做题笔记】UVA11988破损的键盘

    本题可以在洛谷评测,但需要绑定账号 首先解释一下:Home键的作用是把光标移动,End键的作用是返回上次按Home键的地方 考虑朴素做法:输入为[时下一次插入在数组最前端,然后元素整体向后:同时令 l ...

  5. xml配置文件中对于Shiro 权限管理filterChainDefinitions过滤器配置

    博客转载:http://blog.csdn.net/userrefister/article/details/47807075 /** * Shiro-1.2.2内置的FilterChain * @s ...

  6. php preg正则表达式的组成部分

    定界符号 : 多种都可以,常用为// 原子 : 最小的一个匹配单位 (放在定界符中),在一个正则表达式中,至少要有一个原子 1,打印字符(a-z A-Z 0-9 ~!@#$%^&*()_+.. ...

  7. MongoDB_05_更新和删除

    文档的更新和删除 更新文档的方法: db.collection.update(query,update,options) //或 db.collection.update( <query> ...

  8. 【visio】数据可视化 - 链接到外部数据

    编辑数据的时候,纯粹一个一个地手动输入,效率过低,visio提供了连接外部数据的功能,以加快数据导入,该功能也同时能够针对外部数据的改变,更新visio内部数据. 1. 创建外部源数据 visio支持 ...

  9. Atcoder Beginner Contest151E(排列组合)

    排列组合 #define HAVE_STRUCT_TIMESPEC #include<bits/stdc++.h> using namespace std; ]; ; ]; long lo ...

  10. pysftp-tools

    import pysftp import paramiko import os import unittest import json import warnings warnings.filterw ...