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
> In the "Deploy a new AKS cluster" step above we created AKS with Azure CNI, in case you have an existing AKS cluster using [Kubenet mode](../aks/configure-kubenet.md) you need to update the route table to help the packets destined for a POD IP reach the node which is hosting the pod.
105
+
> A simple way to achieve this is by associating the same route table created by AKS to the Application Gateway's subnet.
106
+
107
+
103
108
## Deploy a sample application using AGIC
104
109
105
110
You'll now deploy a sample application to the AKS cluster you created that will use the AGIC add-on for Ingress and connect the application gateway to the AKS cluster. First, you'll get credentials to the AKS cluster you deployed by running the `az aks get-credentials` command.
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/azure-netapp-files-create-volumes.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
40
40
41
41
## Best practice
42
42
43
-
* Ensure that you’re using the proper mount instructions for the volume. See [Mount a volume for Windows or Linux VMs](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md).
43
+
* Ensure that you’re using the proper mount instructions for the volume. See [Mount a volume for Windows or Linux VMs](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md).
44
44
45
45
* The NFS client should be in the same VNet or peered VNet as the Azure NetApp Files volume. Connecting from outside the VNet is supported; however, it will introduce additional latency and decrease overall performance.
46
46
@@ -112,7 +112,7 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
112
112
113
113
Additional configurations are required if you use Kerberos with NFSv4.1. Follow the instructions in [Configure NFSv4.1 Kerberos encryption](configure-kerberos-encryption.md).
114
114
115
-
* If you want to enable Active Directory LDAP users and extended groups (up to 1024 groups) to access the volume, select the **LDAP** option. Follow instructions in [Configure ADDS LDAP with extended groups for NFS volume access](configure-ldap-extended-groups.md) to complete the required configurations.
115
+
* If you want to enable Active Directory LDAP users and extended groups (up to 1024 groups) to access the volume, select the **LDAP** option. Follow instructions in [Configure AD DS LDAP with extended groups for NFS volume access](configure-ldap-extended-groups.md) to complete the required configurations.
116
116
117
117
* Customize **Unix Permissions** as needed to specify change permissions for the mount path. The setting does not apply to the files under the mount path. The default setting is `0770`. This default setting grants read, write, and execute permissions to the owner and the group, but no permissions are granted to other users.
118
118
Registration requirement and considerations apply for setting **Unix Permissions**. Follow instructions in [Configure Unix permissions and change ownership mode](configure-unix-permissions-change-ownership-mode.md).
@@ -121,7 +121,7 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
When you publish your container products to Azure Marketplace, the Azure team validates it to ensure that it's secure. If your container products fail any of the tests, it won't be published. You'll receive an error message that describes the issue.
14
+
15
+
This article explains common error messages during container publishing, along with related solutions.
16
+
17
+
> [!NOTE]
18
+
> If you have questions about this article or suggestions for improvement, contact [Partner Center support](https://go.microsoft.com/fwlink/?linkid=2165533).
19
+
20
+
21
+
sections:
22
+
- name: Ignored
23
+
questions:
24
+
- question: |
25
+
Vulnerability failure
26
+
answer: |
27
+
A vulnerability is an exploitable risk and/or an unsecured entry points that can be used by malicious actors for nefarious actions.
28
+
If you're planning to publish container products, you should scan your product for vulnerability and fix them before publishing the container product.
29
+
If your existing container products have vulnerabilities in them, you should deprecate/hide the affected offer and republish after fixing the vulnerabilities.
30
+
31
+
- question: |
32
+
Malware failure
33
+
answer: |
34
+
A malware, or malicious software, is a file or program that is designed to be harmful to computer, network or servers.
35
+
36
+
If you're planning to publish container products, you should scan your product for malware, identify all files that contain malware and remove them before publishing the container product.
37
+
38
+
If your existing container products have malware, you should deprecate/hide the affected offers and republish the patched product.
39
+
40
+
41
+
additionalContent: |
42
+
43
+
## Next steps
44
+
- [Plan an Azure container offer](marketplace-containers.md)
0 commit comments