"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "docs/content/routing/providers/kubernetes-crd.md" between
traefik-v2.3.2.src.tar.gz and traefik-v2.3.3.src.tar.gz

About: Traefik is a cloud native edge router, a reverse proxy and load balancer for HTTP and TCP-based applications.

kubernetes-crd.md  (traefik-v2.3.2.src):kubernetes-crd.md  (traefik-v2.3.3.src)
skipping to change at line 621 skipping to change at line 621
- name: whoami - name: whoami
port: 80 port: 80
middlewares: middlewares:
- name: stripprefix - name: stripprefix
namespace: foo namespace: foo
``` ```
!!! important "Cross-provider namespace" !!! important "Cross-provider namespace"
As Kubernetes also has its own notion of namespace, one should not confuse t he kubernetes namespace of a resource As Kubernetes also has its own notion of namespace, one should not confuse t he kubernetes namespace of a resource
(in the reference to the middleware) with the [provider namespace](../../mid dlewares/overview.md#provider-namespace), (in the reference to the middleware) with the [provider namespace](../../pro viders/overview.md#provider-namespace),
when the definition of the middleware comes from another provider. when the definition of the middleware comes from another provider.
In this context, specifying a namespace when referring to the resource does not make any sense, and will be ignored. In this context, specifying a namespace when referring to the resource does not make any sense, and will be ignored.
Additionally, when you want to reference a Middleware from the CRD Provider, Additionally, when you want to reference a Middleware from the CRD Provider,
you have to append the namespace of the resource in the resource-name as Tra efik appends the namespace internally automatically. you have to append the namespace of the resource in the resource-name as Tra efik appends the namespace internally automatically.
More information about available middlewares in the dedicated [middlewares secti on](../../middlewares/overview.md). More information about available middlewares in the dedicated [middlewares secti on](../../middlewares/overview.md).
### Kind: `TraefikService` ### Kind: `TraefikService`
`TraefikService` is the CRD implementation of a ["Traefik Service"](../services/ index.md). `TraefikService` is the CRD implementation of a ["Traefik Service"](../services/ index.md).
skipping to change at line 1458 skipping to change at line 1458
data: data:
tls.ca: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCi0tLS0tRU5EIENFUlRJRklDQVRFLS 0tLS0= tls.ca: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCi0tLS0tRU5EIENFUlRJRklDQVRFLS 0tLS0=
``` ```
!!! important "References and namespaces" !!! important "References and namespaces"
If the optional `namespace` attribute is not set, the configuration will be applied with the namespace of the IngressRoute. If the optional `namespace` attribute is not set, the configuration will be applied with the namespace of the IngressRoute.
Additionally, when the definition of the TLS option is from another provi der, Additionally, when the definition of the TLS option is from another provi der,
the cross-provider syntax (`middlewarename@provider`) should be used to r the cross-provider [syntax](../../providers/overview.md#provider-namespac
efer to the TLS option, e) (`middlewarename@provider`) should be used to refer to the TLS option.
just as in the [middleware case](../../middlewares/overview.md#provider-n
amespace).
Specifying a namespace attribute in this case would not make any sense, a nd will be ignored. Specifying a namespace attribute in this case would not make any sense, a nd will be ignored.
### Kind: `TLSStore` ### Kind: `TLSStore`
`TLSStore` is the CRD implementation of a [Traefik "TLS Store"](../../https/tls. md#certificates-stores). `TLSStore` is the CRD implementation of a [Traefik "TLS Store"](../../https/tls. md#certificates-stores).
Register the `TLSStore` kind in the Kubernetes cluster before creating `TLSStore ` objects Register the `TLSStore` kind in the Kubernetes cluster before creating `TLSStore ` objects
or referencing TLS stores in the [`IngressRoute`](#kind-ingressroute) / [`Ingres sRouteTCP`](#kind-ingressroutetcp) objects. or referencing TLS stores in the [`IngressRoute`](#kind-ingressroute) / [`Ingres sRouteTCP`](#kind-ingressroutetcp) objects.
!!! important "Default TLS Store" !!! important "Default TLS Store"
skipping to change at line 1492 skipping to change at line 1491
name: default name: default
namespace: default namespace: default
spec: spec:
defaultCertificate: defaultCertificate:
secretName: mySecret # [1] secretName: mySecret # [1]
``` ```
| Ref | Attribute | Purpose | | Ref | Attribute | Purpose |
|-----|-----------------------------|------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------| |-----|-----------------------------|------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------|
| [1] | `secretName` | The name of the referenced Kubernetes [Sec ret](https://kubernetes.io/docs/concepts/configuration/secret/) that holds the d efault certificate for the store. | | [1] | `secretName` | The name of the referenced Kubernetes [Sec ret](https://kubernetes.io/docs/concepts/configuration/secret/) that holds the d efault certificate for the store. |
??? example "Declaring and referencing a TLSStore" ??? example "Declaring and referencing a TLSStore"
```yaml tab="TLSStore" ```yaml tab="TLSStore"
apiVersion: traefik.containo.us/v1alpha1 apiVersion: traefik.containo.us/v1alpha1
kind: TLSStore kind: TLSStore
metadata: metadata:
name: default name: default
namespace: default namespace: default
 End of changes. 3 change blocks. 
6 lines changed or deleted 4 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)