Kubernetes Core
- By Canonical Kubernetes | bundle
- Cloud
Channel | Revision | Published |
---|---|---|
latest/stable | 1845 | 04 Sep 2024 |
latest/candidate | 1826 | 16 Apr 2024 |
latest/beta | 1843 | 15 Aug 2024 |
latest/edge | 1841 | 02 Aug 2024 |
1.32/edge | 1846 | 10 Sep 2024 |
1.31/stable | 1844 | 04 Sep 2024 |
1.31/beta | 1842 | 12 Aug 2024 |
1.31/edge | 1840 | 02 Aug 2024 |
1.30/stable | 1834 | 11 Jul 2024 |
1.30/beta | 1831 | 18 Apr 2024 |
1.30/edge | 1839 | 26 Jul 2024 |
1.29/stable | 1823 | 12 Feb 2024 |
1.29/candidate | 1827 | 16 Apr 2024 |
1.29/beta | 1822 | 12 Feb 2024 |
1.29/edge | 1818 | 13 Dec 2023 |
1.28/stable | 1817 | 21 Aug 2023 |
1.28/candidate | 1809 | 07 Jun 2023 |
1.28/beta | 1816 | 21 Aug 2023 |
1.28/edge | 1811 | 07 Aug 2023 |
1.27/stable | 1805 | 21 Apr 2023 |
1.27/candidate | 1807 | 17 May 2023 |
1.27/beta | 1802 | 09 Apr 2023 |
1.27/edge | 1799 | 23 Feb 2023 |
1.26/stable | 1794 | 15 Dec 2022 |
1.26/candidate | 1796 | 13 Jan 2023 |
1.26/beta | 1801 | 08 Apr 2023 |
1.26/edge | 1786 | 22 Nov 2022 |
1.25/stable | 1779 | 01 Sep 2022 |
1.25/candidate | 1780 | 09 Sep 2022 |
1.25/beta | 1788 | 01 Dec 2022 |
1.25/edge | 1775 | 17 Aug 2022 |
1.24/stable | 1748 | 04 Aug 2022 |
1.24/candidate | 1742 | 02 Aug 2022 |
1.24/beta | 1605 | 06 May 2022 |
1.24/edge | 1772 | 15 Aug 2022 |
1.23/edge | 1542 | 16 Mar 2022 |
juju deploy kubernetes-core
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
-
bgp-service-cluster-ips | string
Space-separated list of service cluster CIDRs to advertise over BGP. These will be passed to the .spec.serviceClusterIPs field of the default BGPConfiguration in Calico. Example value: ”10.0.0.0/24 10.0.1.0/24”
-
bgp-service-external-ips | string
Space-separated list of service external CIDRs to advertise over BGP. These will be passed to the .spec.serviceExternalIPs field of the default BGPConfiguration in Calico. Example value: ”10.0.0.0/24 10.0.1.0/24”
-
bgp-service-loadbalancer-ips | string
Space-separated list of service load-balancer CIDRs to advertise over BGP. These will be passed to the .spec.serviceLoadBalancerIPs field of the default BGPConfiguration in Calico. Example value: ”10.0.0.0/24 10.0.1.0/24”
-
cidr | string
Default: 192.168.0.0/16
Network CIDR assigned to Calico. This is applied to the default Calico pool, and is also communicated to the Kubernetes charms for use in kube-proxy configuration. Calico assigns IP addresses to Kubernetes nodes in blocks of 64 addresses. It is recommended to make the Calico network large enough to assign at least one 64 address block to each kubernetes-control-plane and kubernetes-worker unit.
-
disable-vxlan-tx-checksumming | boolean
Default: True
When set to true, if VXLAN encapsulation is in use, then the charm will disable TX checksumming on the vxlan.calico network interface. This works around an upstream issue in Calico: https://github.com/projectcalico/calico/issues/3145
-
global-as-number | int
Default: 64512
Global AS number.
-
global-bgp-peers | string
Default: []
List of global BGP peers. Each BGP peer is specified with an address and an as-number. Example value: "[{address: 10.0.0.1, as-number: 65000}, {address: 10.0.0.2, as-number: 65001}]"
-
ignore-loose-rpf | boolean
Enable or disable IgnoreLooseRPF for Calico Felix. This is only used when rp_filter is set to a value of 2.
-
image-registry | string
Default: rocks.canonical.com:443/cdk
Source registry of Calico images. By setting to a value, each image listed in the releases manifest has its image-registry replaced.
-
ipip | string
Default: Never
IPIP encapsulation mode. Must be one of "Always", "CrossSubnet", or "Never". This is incompatible with VXLAN encapsulation. If VXLAN encapsulation is enabled, then this must be set to "Never".
-
manage-pools | boolean
Default: True
If true, a default pool is created using the cidr and ipip charm configuration values. Warning: When manage-pools is enabled, the charm will delete any pools that are unrecognized.
-
nat-outgoing | boolean
Default: True
NAT outgoing traffic
-
node-to-node-mesh | boolean
Default: True
When enabled, each Calico node will peer with every other Calico node in the cluster.
-
release | string
Version of Calico to deploy
-
route-reflector-cluster-ids | string
Default: {}
Mapping of unit IDs to route reflector cluster IDs. Assigning a route reflector cluster ID allows the node to function as a route reflector. Example value: "{0: 224.0.0.1, 2: 224.0.0.1}"
-
subnet-as-numbers | string
Default: {}
Mapping of subnets to AS numbers, specified as YAML. Each Calico node will be assigned an AS number based on the entries in this mapping. Example value: "{10.0.0.0/24: 64512, 10.0.1.0/24: 64513}" If a node's IP matches any of the specified subnets, then the corresponding AS number is used instead of the global one. If a node's IP matches no subnets, then the global AS number will be used instead. If a node's IP matches multiple subnets, then the most specific subnet will be used, e.g. a /24 subnet will take precedence over a /16.
-
subnet-bgp-peers | string
Default: {}
Mapping of subnets to lists of BGP peers. Each BGP peer is specified with an address and an as-number. Example value: "{10.0.0.0/24: [{address: 10.0.0.1, as-number: 65000}, {address: 10.0.0.2, as-number: 65001}], 10.0.1.0/24: [{address: 10.0.1.1, as-number: 65002}]}" If a node's IP matches multiple subnets, then peerings will be added for each matched subnet.
-
unit-as-numbers | string
Default: {}
Mapping of unit IDs to AS numbers, specified as YAML. Each Calico node will be assigned an AS number based on the entries in this mapping. Example value: "{0: 64512, 1: 64513}" This takes precedence over global-as-number and subnet-as-numbers.
-
unit-bgp-peers | string
Default: {}
Mapping of unit IDs to lists of BGP peers. Each BGP peer is specified with an address and an as-number. Example value: "{0: [{address: 10.0.0.1, as-number: 65000}, {address: 10.0.0.2, as-number: 65001}], 1: [{address: 10.0.1.1, as-number: 65002}]}"
-
veth-mtu | int
Set veth MTU size. This should be set to the MTU size of the base network. If VXLAN is enabled, then the charm will automatically subtract 50 from the specified MTU size. If IPIP is enabled, then the charm will automatically subtract 20 from the specified MTU size.
-
vxlan | string
Default: Never
VXLAN encapsulation mode. Must be one of "Always", "CrossSubnet", or "Never". This is incompatible with IPIP encapsulation. If IPIP encapsulation is enabled, then this must be set to "Never".