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
{{ message }}
This repository was archived by the owner on Mar 16, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: docs/docs/100-reference/01-command-line/acorn_install.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,7 @@ acorn install
21
21
```
22
22
--acorn-dns string enabled|disabled|auto. If enabled, containers created by Acorn will get public FQDNs. Auto functions as disabled if a custom clusterDomain has been supplied (default auto)
23
23
--acorn-dns-endpoint string The URL to access the Acorn DNS service
24
+
--allow-traffic-from-namespace strings Namespaces that are allowed to send network traffic to all Acorn apps
24
25
--allow-user-annotation strings Allow these annotations to propagate to dependent objects, no effect if --ignore-user-labels-and-annotations not true
25
26
--allow-user-label strings Allow these labels to propagate to dependent objects, no effect if --ignore-user-labels-and-annotations not true
26
27
--api-server-replicas int acorn-api deployment replica count
@@ -33,12 +34,14 @@ acorn install
33
34
--ignore-user-labels-and-annotations Don't propagate user-defined labels and annotations to dependent objects
34
35
--image string Override the default image used for the deployment
35
36
--ingress-class-name string The ingress class name to assign to all created ingress resources (default '')
37
+
--ingress-controller-namespace string The namespace where the ingress controller runs - used to secure published HTTP ports with NetworkPolicies.
36
38
--internal-cluster-domain string The Kubernetes internal cluster domain (default svc.cluster.local)
37
39
--internal-registry-prefix string The image prefix to use when pushing internal images (example ghcr.io/my-org/)
38
40
--lets-encrypt string enabled|disabled|staging. If enabled, acorn generated endpoints will be secured using TLS certificate from Let's Encrypt. Staging uses Let's Encrypt's staging environment. (default disabled)
39
41
--lets-encrypt-email string Required if --lets-encrypt=enabled. The email address to use for Let's Encrypt registration(default '')
40
42
--lets-encrypt-tos-agree Required if --lets-encrypt=enabled. If true, you agree to the Let's Encrypt terms of service (default false)
41
43
--manage-volume-classes Manually manage volume classes rather than sync with storage classes, setting to 'true' will delete Acorn-created volume classes
Copy file name to clipboardExpand all lines: docs/docs/30-installation/02-options.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,6 +94,13 @@ The default installation of Acorn will automatically create and sync any storage
94
94
95
95
If an admin would rather manually manage the volume classes and not have these generated ones, then the `--manage-volume-classes` installation flag is available. The generated volume classes are not generated if this flag is used, and are deleted when the flag is set on an existing Acorn installation. If the flag is again switched off with `--manage-volume-classes=false`, then the volume classes will be generated again.
96
96
97
+
## Kubernetes NetworkPolicies
98
+
By default, Acorn will automatically create and manage Kubernetes [NetworkPolicies](https://kubernetes.io/docs/concepts/services-networking/network-policies/) to isolate Acorn projects on the network level. This behavior can be disabled by passing `--network-policies=false` to `acorn install`, and can later be re-enabled by passing `--network-policies=true`.
99
+
100
+
By default, Acorn workloads that publish ports that use HTTP will be allowed to receive traffic from internal (other pods in the cluster) and external (through the cluster's ingress) sources. To secure this further, you can require all traffic to Acorn workloads flow through your ingress by specifying the `--ingress-controller-namespace` parameter during installation.
101
+
102
+
To allow traffic from a specific namespace to all Acorn apps in the cluster, use `--allow-traffic-from-namespace=<namespace>`. This is useful if there is a monitoring namespace, for example, that needs to be able to connect to all the pods created by Acorn in order to scrape metrics.
103
+
97
104
## Changing install options
98
105
If you want to change your installation options after the initial installation, just rerun `acorn install` with the new options. This will update the existing install dynamically.
Copy file name to clipboardExpand all lines: pkg/apis/api.acorn.io/v1/types.go
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -346,6 +346,9 @@ type Config struct {
346
346
PropagateProjectAnnotations []string`json:"propagateProjectAnnotations" name:"propagate-project-annotation" usage:"The list of keys of annotations to propagate from acorn project to app namespaces"`
347
347
PropagateProjectLabels []string`json:"propagateProjectLabels" name:"propagate-project-label" usage:"The list of keys of labels to propagate from acorn project to app namespaces"`
348
348
ManageVolumeClasses*bool`json:"manageVolumeClasses" name:"manage-volume-classes" usage:"Manually manage volume classes rather than sync with storage classes, setting to 'true' will delete Acorn-created volume classes"`
IngressControllerNamespace*string`json:"ingressControllerNamespace" name:"ingress-controller-namespace" usage:"The namespace where the ingress controller runs - used to secure published HTTP ports with NetworkPolicies."`
351
+
AllowTrafficFromNamespace []string`json:"allowTrafficFromNamespace" name:"allow-traffic-from-namespace" usage:"Namespaces that are allowed to send network traffic to all Acorn apps"`
0 commit comments