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
Copy file name to clipboardExpand all lines: charts/self-host/README.md
+24-16Lines changed: 24 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -561,43 +561,51 @@ secrets:
561
561
secretProviderClass: bitwarden-azure-keyvault-csi #metadata.name in example
562
562
```
563
563
564
+
### Create Empty Azure Application Gateway Rewrite Set
565
+
566
+
Application Gateway ingress deployments have a few more required step for Bitwarden to function correctly. If you are using another ingress controller, you may skip to the next section.
567
+
568
+
We will need to create a rewrite set on the Application Gateway. There are various ways of doing this, but we will discuss using the Azure Portal. For now we are creating an empty set for the Helm deployment to work. We will add the rewrite rule after deploying Helm.
569
+
570
+
1. Navigate to the Application Gateway in the Azure Portal
571
+
2. Once in the Application Gateway, find the "Rewrites" blade in the left-hand navigation menu.
572
+
3. Click the "+ Rewrite set" button at the top of the main page section to add a new rewrite set
573
+
4. On the "Update rewrite set" page in the "Name and Association" tab set the `Name` field to the same value specified in the `appgw.ingress.kubernetes.io/rewrite-rule-set` ingress annotation
Application Gateway ingress deployments have one more required step for Bitwarden to function correctly. If you are using another ingress controller, you may skip to the next section.
573
586
574
-
We will need to create a rewrite set on the Application Gateway. There are various ways of doing this, but we will discuss using the Azure Portal.
587
+
We will need finish the rewrite set on the Application Gatewaywe created earlier.
575
588
576
-
1. Navigate to the Application Gateway in the Azure Portal
577
-
2. Once in the Application Gateway, find the "Rewrites" blade in the left-hand navigation menu.
578
-
3. Click the "+ Rewrite set" button at the top of the main page section to add a new rewrite set
579
-
4. On the "Update rewrite set" page in the "Name and Association" tab:
580
-
- Set the Name field to the same value specified in the `appgw.ingress.kubernetes.io/rewrite-rule-set` ingress annotation
581
-
- Select all routing rules that start with something similar to "pr-bitwarden-bitwarden-ingress-rule-*"
582
-
5. Click Next
583
-
6. On the "Rewrite rule configuration" tab, click the "Add rewrite rule" button
584
-
7. Enter a name for the rule. This can be anything that helps you with organization. Something simlar to "bitwarden-rewrite" will work.
585
-
8. The rule sequence value does not matter for this purpose.
586
-
9. Add a condition and set the following values:
589
+
1. Reopen the rewrite set you created earlier.
590
+
2. On the "Update rewrite set" page in the "Name and Association" tab, select all routing paths that begin with pr-bitwarden-self-host-ingress... , de-select any that do not begin with that prefix, and select Next
591
+
3. On the "Rewrite rule configuration" tab, click the "Add rewrite rule" button
592
+
4. Enter a name for the rule. This can be anything that helps you with organization. Something simlar to "bitwarden-rewrite" will work.
593
+
5. The rule sequence value does not matter for this purpose.
0 commit comments