This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About cpazdersky
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About cpazdersky
05-08-2023
1Post
0Likes
0Solutions
May 08, 2023Last Visited
User
Activity
User
Profile
Latest posts by cpazdersky
| Subject | Views | Posted |
|---|---|---|
| 265 | 05-08-2023 07:41 AM |
User Badges
Community Statistics
| Member Since | 05-08-2023 07:24 AM |
| Date Last Visited | 05-08-2023 12:00 PM |
| Posts | 1 |
05-08-2023
07:41 AM
PCC self-hosted on Azure Kubernetes Service, sits behind an App Gateway that serves as a proxy/ingress/firewall
Attempting to deploy defenders to VMs that sit outside the App Gateway - connectivity fails through the ingress to the Console regardless of configuration of Defender, Ingress, or Console. Even traffic that we allow through the ingress fails to reach the console on 8084
Attempting to deploy supervisor consoles- connectivity fails because the master console requires a URL with a port appended to it (why?) - this fails to connect through an ingress that listens on 80/443 as well because of the 8083 port requirement on the URL
As it sits, the only resources that can connect to the master console are other resources behind the app gateway on the same AKS Cluster
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
05-08-2023
12:00 PM
|
Latest Tags
No tags yet
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks