Skip to content

Commit 74977c6

Browse files
authored
Merge pull request #211673 from MicrosoftDocs/main
merge main to Live, Sunday 4 PM
2 parents fc571fc + 441b373 commit 74977c6

File tree

5 files changed

+59
-6
lines changed

5 files changed

+59
-6
lines changed

articles/application-gateway/tutorial-ingress-controller-add-on-existing.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,11 @@ appGWVnetId=$(az network vnet show -n myVnet -g myResourceGroup -o tsv --query "
100100
az network vnet peering create -n AKStoAppGWVnetPeering -g $nodeResourceGroup --vnet-name $aksVnetName --remote-vnet $appGWVnetId --allow-vnet-access
101101
```
102102

103+
> [!NOTE]
104+
> 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+
103108
## Deploy a sample application using AGIC
104109

105110
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.

articles/azure-netapp-files/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -348,7 +348,7 @@
348348
- name: Pricing
349349
href: https://azure.microsoft.com/pricing/details/netapp/
350350
- name: Regional availability
351-
href: https://azure.microsoft.com/global-infrastructure/services/?products=netapp
351+
href: https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=netapp&rar=true&regions=all
352352
- name: SLA
353353
href: https://azure.microsoft.com/support/legal/sla/netapp/
354354
- name: Videos

articles/azure-netapp-files/azure-netapp-files-create-volumes.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
4040

4141
## Best practice
4242

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).
4444

4545
* 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.
4646

@@ -112,7 +112,7 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
112112

113113
Additional configurations are required if you use Kerberos with NFSv4.1. Follow the instructions in [Configure NFSv4.1 Kerberos encryption](configure-kerberos-encryption.md).
114114

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.
116116

117117
* 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.
118118
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
121121

122122
![Specify NFS protocol](../media/azure-netapp-files/azure-netapp-files-protocol-nfs.png)
123123

124-
4. Click **Review + Create** to review the volume details. Then click **Create** to create the volume.
124+
4. Click **Review + Create** to review the volume details. Then click **Create** to create the volume.
125125

126126
The volume you created appears in the Volumes page.
127127

@@ -131,8 +131,8 @@ This article shows you how to create an NFS volume. For SMB volumes, see [Create
131131

132132
* [Configure NFSv4.1 default domain for Azure NetApp Files](azure-netapp-files-configure-nfsv41-domain.md)
133133
* [Configure NFSv4.1 Kerberos encryption](configure-kerberos-encryption.md)
134-
* [Enable Active Directory Domain Services (ADDS) LDAP authentication for NFS volumes](configure-ldap-over-tls.md)
135-
* [Configure ADDS LDAP with extended groups for NFS volume access](configure-ldap-extended-groups.md)
134+
* [Enable Active Directory Domain Services (AD DS) LDAP authentication for NFS volumes](configure-ldap-over-tls.md)
135+
* [Configure AD DS LDAP with extended groups for NFS volume access](configure-ldap-extended-groups.md)
136136
* [Mount a volume for Windows or Linux VMs](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md)
137137
* [Configure export policy for an NFS volume](azure-netapp-files-configure-export-policy.md)
138138
* [Configure Unix permissions and change ownership mode](configure-unix-permissions-change-ownership-mode.md).

articles/marketplace/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -209,6 +209,8 @@
209209
href: azure-container-plan-availability.md
210210
- name: Plan technical configuration
211211
href: azure-container-plan-technical-configuration.md
212+
- name: Container certification troubleshooting
213+
href: azure-container-certification-faq.yml
212214
- name: Azure virtual machine offer
213215
items:
214216
- name: Plan the offer
Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
### YamlMime:FAQ
2+
metadata:
3+
title: Container certification troubleshooting for Azure Marketplace
4+
description: Troubleshoot common issues related to testing and certifying container products for Azure Marketplace.
5+
ms.service: marketplace
6+
ms.subservice: partnercenter-marketplace-publisher
7+
ms.topic: faq
8+
author: mathapli
9+
ms.author: mathapli
10+
ms.date: 09/27/2021
11+
title: Troubleshoot container certification
12+
summary: |
13+
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)
45+
- [Active marketplace rewards](marketplace-rewards.md)
46+
- If you have questions or feedback for improvement, contact [Partner Center support](https://go.microsoft.com/fwlink/?linkid=2165533)

0 commit comments

Comments
 (0)