You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the inter-container communication is enabled in `swarm` either by `network` or `link`, in `k8s` if you have more than one service and they need to communicate together, you will need to expose the ports explicitly by `--set services.XXX.expose={YYYY}`
15
15
16
16
# Features (complete)
17
-
The chart is quite features complete and I was able to deploy complex stacks with it including `traefik` and `kubernetes-dashboard`. In all cases, there is a mechanism to override the generated manifests with full possibilities of `k8s` API (see below.)
17
+
The chart is features complete and I was able to deploy complex stacks with it including `traefik` and `kubernetes-dashboard`. In all cases, there is a mechanism to override the generated manifests with full possibilities of `k8s` API (see below.)
18
18
19
-
Acceptable configurations can be found in the [test](./docker-compose-redmine.yaml):.
19
+
Acceptable configurations can be found in the [test](./test/docker-compose-redmine.yaml):.
20
20
21
21
-[X] Deployment:
22
22
- Default to `Deployment`
@@ -31,31 +31,30 @@ Acceptable configurations can be found in the [test](./docker-compose-redmine.ya
31
31
-[X] Resources:
32
32
-`deploy.resources.reservations` map to `request` and
33
33
-`deploy.resources.limits` map to `limit` (accept both `cpus` and `cpu` keys)
34
-
-[X] Toleration: via extra key `deploy.placement.tolerations` with `kubectl taint` syntax
35
-
-[X] Resources: `deploy.resource.reservations` map to `request` and `deploy.resource.limits` map to `limit` (accept both `cpus` and `cpu`!)
34
+
-[X] Toleration: via [extra key](#extra-keys)`deploy.placement.tolerations` with `kubectl taint` syntax
36
35
-[X] Service:
37
36
-`ports` expose `LoadBlancer` by default
38
37
-`expose` exposes `ClusterIP` services
39
38
-`nodePorts` expose `NodePort` services
40
39
-[X] Ingress
41
-
- Support `traefik` (1.7) labels (`deploy.labels`) as input with annotations including basic auth
42
-
- Support `CertManager``Issuer` and `ClusterIssuer` via extra labels `traefik.issuer` and `traefik.cluster-issuer`
40
+
- Support `traefik` (1.7) labels (`deploy.labels`) as input with annotations support, including basic auth, `PathPrefixStrip`, `customRequestHeaders`, `customResponseHeaders`...
41
+
- Support `CertManager`'s`Issuer` and `ClusterIssuer` via extra labels `traefik.issuer` and `traefik.cluster-issuer`
43
42
- Support `Ingress` class via extra label `traefik.ingress-class`
44
43
- Support `segment` labels for services that expose multiple ports `traefik.port`, `traefik.first.port`, `traefik.second.port`...
45
-
- Advanced features (`PathPrefixStrip`, custom headers...) will set the Ingress class to `traefik`, but again it can be overwritten.
-[X] Volume: Support inline/top-level volumes/external volumes
45
+
- Support both short and long syntax
47
46
- Automatic switch to `volumeClaimTemplates` for `StatefulSet` (really useful if combine with cloud provider's dynamic provisioner).
48
-
- Dynamic provisioner should work as expected `volumes.XXX.driver_opts.type` maps directly to `storageClassName` including treatments for
47
+
- Dynamic provisioner should work as expected.`volumes.XXX.driver_opts.type` maps directly to `storageClassName` including treatments for:
49
48
-`none` (default storage class)
50
49
-`nfs`
51
50
-`emptyDir`
52
-
- Support `none` (map to `hostPath` if `volumes.XXX.driver_opts.device` presents) and `nfs` (support`addr` in `volumes.XXX.driver_opts.o`, `volumes.XXX.driver_opts.device`) static provisioner.
53
-
- Support `readOnly` attribute (`volume:/path:ro`)
- Support `none` (map to `hostPath` if `volumes.XXX.driver_opts.device` presents) and `nfs` (if`addr`presents in `volumes.XXX.driver_opts.o` and `volumes.XXX.driver_opts.device` prensents) static provisioner.
52
+
- Support `readOnly` attribute (`volume:/path:ro` style)
53
+
-[X] Config: Support top-level configs/external configs
55
54
- Support both short and long syntax
56
55
- Data can be integrated directly via `data` external key
57
56
- Support mouting as directory by setting `file` to null. See [Advance: full override](#advance-full-override) to see how to insert more than one files
-[X] Secret: Support top-level secrets/external secrets
59
58
- Support both short and long syntax
60
59
- Data can be integrated directly via `data` and `stringData` external keys
61
60
- Support mouting as directory by setting `file` to null. See [Advance: full override](#advance-full-override) to see how to insert more than one files
@@ -70,7 +69,7 @@ Acceptable configurations can be found in the [test](./docker-compose-redmine.ya
70
69
Tested in a K3s cluster with `local-path` provisioner.
0 commit comments