-
Notifications
You must be signed in to change notification settings - Fork 122
/
Copy pathstuff.txt
1604 lines (1604 loc) · 352 KB
/
stuff.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
./calico-enterprise_versioned_docs/version-3.18-2/_includes/content/_default-install.mdx:6:| User interface | the $[prodname] web console user interface (with a default of “no access outside the cluster”). |
./calico-enterprise_versioned_docs/version-3.18-2/_includes/content/_license.mdx:9:### Does the web console display license expiration?
./calico-enterprise_versioned_docs/version-3.18-2/_includes/content/_license.mdx:11:Yes. The license indicator in the web console (top right banner) turns red when the license expires.
./calico-enterprise_versioned_docs/version-3.18-2/_includes/content/_license.mdx:19:Although users can still log in to the web console, your deployment is no longer operational. All policy enforcement stops, except for policies in the default tier. In most cases, you will experience broken connectivity (depending on your policies in the default tier). $[prodname] stops reporting flow logs, DNS logs, and $[prodname] metrics, which affects other UI elements like Service Graph and dashboards. Although some elements may appear to work, actions are not saved, and you should regard your deployment as non-functional. We recommend that you proactively manage your license to avoid disruption.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/application-layer-policies/alp-tutorial.mdx:86:is that you'll see HTTP traffic flows in the web console in features like Service Graph.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/policy-firewalls/aws-integration/tiers-and-policy.mdx:33:We recommend restricting access to integration tiers to ensure they are not modified as they are essential to operations. When you log in to the $[prodname] web console, the following integration tiers are displayed.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/policy-firewalls/fortinet-integration/overview.mdx:33:**Solution**: Use FortiManager to create firewall policies that are applied as $[prodname] network policies on Kubernetes workloads. Use the power of a $[prodname] “higher-order tier” so Kubernetes policy is evaluated early in the policy processing order, but update policy using FortiManager UI. Use the $[prodname] web console as a secondary interface to verify the integration and troubleshoot using logs.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:29:1. Use the $[prodname] web console to verify the integration, and then FortiManager UI to make all updates to policy rules.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:47:- Login access to [the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:65:Create a [$[prodname] tier](../../policy-tiers/tiered-policy.mdx) in the $[prodname] web console for each Kubernetes cluster you want to secure. We recommend that you create a new tier (rather than reusing an existing tier) for all global network policies created by the $[prodname] integration controller.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:110: | tier | Tier name you created in the web console |
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:154:5. Log in to the $[prodname] web console, and under the tier that you specified in the ConfigMap, verify that the GlobalNetworkPolicies are created.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/policy-tiers/tiered-policy.mdx:29:To create a tier and policy in the web console:
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/policy-tiers/policy-tutorial-ui.mdx:9:- How to create a policy in the web console
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/policy-tiers/policy-tutorial-ui.mdx:32:To follow along in the web console, click **Policies**.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/policy-tiers/rbac-tiered-policies.mdx:26:In $[prodname], global network policy and network policy resources are associated with a specific tier. Admins can configure access control for these $[prodname] policies using standard Kubernetes `Role` and `ClusterRole` resource types. This makes it easy to manage RBAC for both Kubernetes network policies and $[prodname] tiered network policies. RBAC permissions include managing resources using the $[prodname] web console, and `kubectl`.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/policy-tiers/rbac-tiered-policies.mdx:90:Create an Admin user with full access to the $[prodname] web console (as well as everything else in the cluster) using the following command. See the Kubernetes documentation to identify users based on your chosen [authentication method](https://kubernetes.io/docs/reference/access-authn-authz/authentication/), and how to use the [RBAC resources](https://kubernetes.io/docs/reference/access-authn-authz/rbac/).
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/policy-tiers/rbac-tiered-policies.mdx:100:All users using the $[prodname] web console should be able to create authorizationreviews and authorizationrequests as well as access
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/policy-tiers/rbac-tiered-policies.mdx:373:tier. This has the effect of making the **net-sec** tier visible in the $[prodname] web console (including listing the names of the policies it contains).
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/policy-best-practices.mdx:329:A big obstacle to adopting Kubernetes is not having confidence that you can effectively prevent, detect, and mitigate across diverse teams. The following policy life cycle tools in the web console (**Policies** tab) can help.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/recommendations/learn-about-policy-recommendations.mdx:31:1. In the web console left navbar, click the **Policies** icon.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/recommendations/learn-about-policy-recommendations.mdx:96:1. In the web console left navbar, click **Service Graph**.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/recommendations/policy-recommendations.mdx:37:Basic knowledge of policies in the web console and tiers:
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/recommendations/policy-recommendations.mdx:43:Creating and managing policy recommendations is available only in the web console.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/recommendations/policy-recommendations.mdx:57:1. In the left navbar in the web console, click **Policies**, **Recommendations**.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/beginners/calico-labels.mdx:118:$[prodname] labels must be used with the correct selector or the policy will not work as designed (and there are no error messages in the web console or when applying the YAML).
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/beginners/simple-policy-cnx.mdx:161: Alternatively, you may also use the $[prodname] web console to inspect and view information and metrics associated with policies, endpoints, and nodes.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/beginners/simple-policy-cnx.mdx:218:In the $[prodname] web console, head to the dashboard view. You will see graphs associated with allowed packets/bytes and denied packets/bytes. The graphs represent the rates at which packets/bytes are being allowed or denied and are time windowed.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/networksets.mdx:21:If you are familiar with Service Graph in the web console, you know the value of seeing pod-to-pod traffic within your cluster. But what about traffic external to your cluster?
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/networksets.mdx:53:In this section, we’ll walk through how to create a namespaced network set in the web console. You can follow along using your cluster or tigera-labs cluster.
./calico-enterprise_versioned_docs/version-3.18-2/network-policy/policy-impact-preview.mdx:23:1. From the Edit Policy page on the web console, modify any attribute of the policy.
./calico-enterprise_versioned_docs/version-3.18-2/visibility/alerts.mdx:18:You can manage alerts and alert events in the web console, or using the CLI. $[prodname] also provides alert templates
./calico-enterprise_versioned_docs/version-3.18-2/visibility/alerts.mdx:31:- [Manage alerts in the web console](#manage-alerts-in-manager-ui)
./calico-enterprise_versioned_docs/version-3.18-2/visibility/alerts.mdx:34:### Manage alerts in the web console
./calico-enterprise_versioned_docs/version-3.18-2/visibility/alerts.mdx:36:You can view alert events in the web console in several places: the **Alerts** page, **Service Graph**, and the **Kibana** dashboard.
./calico-enterprise_versioned_docs/version-3.18-2/visibility/alerts.mdx:116:1. In the web console, go to the **Alerts** page to view alert events.
./calico-enterprise_versioned_docs/version-3.18-2/visibility/packetcapture.mdx:13:$[prodname] packet capture is implemented in a Kubernetes-native way so you can troubleshoot service/application connectivity issues and performance issues. You can start a packet capture in the web console Service Graph, or using the CLI.
./calico-enterprise_versioned_docs/version-3.18-2/visibility/kube-audit.mdx:28:### Audit logs in the web console
./calico-enterprise_versioned_docs/version-3.18-2/visibility/kube-audit.mdx:30:Like $[prodname] audit logs, Kubernetes audit logs are displayed in the web console in the Timeline dashboard, Kibana dashboard (indexed by, `tigera_secure_ee_audit_kube`), and provide the core data for compliance reports.
./calico-enterprise_versioned_docs/version-3.18-2/visibility/kibana.mdx:24:In the web console, from the left navbar select, **Kibana**. A new browser tab opens into Kibana.
./calico-enterprise_versioned_docs/version-3.18-2/visibility/kibana.mdx:109:The Honeypod dashboard returns cluster-level information on workloads that have connected to Honeypod resources. These events also generate [GlobalAlerts](../reference/resources/globalalert.mdx), which populate the Alerts table in the web console.
./calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/audit-overview.mdx:27:### Audit logs in the web console
./calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/audit-overview.mdx:29:$[prodname] audit logs are displayed in the Timeline dashboard in the web console. You can filter logs, and export data in .json or .yaml formats.
./calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/rbac-elasticsearch.mdx:19:Elasticsearch resources are associated with the **Kubernetes API group**, `lma.tigera.io`. You can grant access to resources per cluster. The default cluster name for $[prodname] is, `cluster`. As shown in the following table, each Elasticsearch resource is mapped to a specific RBAC resource name within the `lma.tigera.io` API group. In the $[prodname] web console, Elasticsearch resources are called, **indexes or indices**.
./calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/rbac-elasticsearch.mdx:42:- A `tigera-network-admin` role with full permissions to create and modify resources. For help, see [Log in to the $[prodname] web console](../../operations/cnx/authentication-quickstart.mdx).
./calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/rbac-elasticsearch.mdx:44:- To view Elasticsearch resources in the $[prodname] web console, users must have [minimum permissions](../../network-policy/policy-tiers/rbac-tiered-policies.mdx).
./calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/overview.mdx:17:- View Elasticsearch logs in the $[prodname] web console (Kibana dashboard and Flow Visualizer), and the [Elasticsearch API](https://www.elastic.co/guide/en/elasticsearch/reference/current/search.html)
./calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/index.mdx:2:description: Configure logs for visibility in the web console.
./calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/troubleshoot.mdx:52:Be aware that removing LogStorage temporarily removes Elasticsearch from your cluster. Features that depend on LogStorage are temporarily unavailable, including the dashboards in the web console. Data ingestion is also temporarily paused, but will resume when the LogStorage is up and running again.
./calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/l7/configure.mdx:29:L7 logs are visible in the web console, service graph, in the HTTP tab.
./calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/l7/configure.mdx:52:- [View L7 logs in the web console](#view-l7-logs-in-manager-ui)
./calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/l7/configure.mdx:128:### View L7 logs in the web console
./calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/l7/configure.mdx:134:1. In the web console left navbar, click **Service Graph**.
./calico-enterprise_versioned_docs/version-3.18-2/visibility/elastic/l7/configure.mdx:143:1. In the web console left navbar, click **Kibana**.
./calico-enterprise_versioned_docs/version-3.18-2/visibility/get-started-cem.mdx:2:description: Tour the main features of the web console.
./calico-enterprise_versioned_docs/version-3.18-2/visibility/get-started-cem.mdx:12:Let's go through each item in the web console left navbar from top to bottom. You can follow along using any cluster.
./calico-enterprise_versioned_docs/version-3.18-2/visibility/get-started-cem.mdx:110:This page is where you switch views between clusters in the web console. When you connect to a different cluster, the entire web console view changes to reflect the selected cluster.
./calico-enterprise_versioned_docs/version-3.18-2/networking/egress/troubleshoot.mdx:220:In [the web console](../../visibility/get-started-cem.mdx), check for dropped packets because of policy on the outbound connection path. If you are using the iptables data plane, you can also run the following command on the client and gateway nodes to look at a lower level.
./calico-enterprise_versioned_docs/version-3.18-2/networking/configuring/multiple-networks.mdx:67:- [Install and configure calicoctl](../../operations/clis/calicoctl/index.mdx) or configure access to [the web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/networking/configuring/multiple-networks.mdx:198:**In the $[prodname] web console**, go to the **WorkloadEndpoint** page to see all of the WorkloadEndpoints, including the network labels are for targeting WorkloadEndpoints with policy.
./calico-enterprise_versioned_docs/version-3.18-2/threat/honeypods.mdx:27:Honeypods can be configured on a per-cluster basis using "template" honeypod manifests that are easily customizable. Any alerts triggered are displayed in the Alerts tab in the $[prodname] web console. The Honeypod Dashboard in Kibana provides an easy way to monitor and analyze traffic reaching the honeypods.
./calico-enterprise_versioned_docs/version-3.18-2/threat/suspicious-domains.mdx:50:#### Using the web console
./calico-enterprise_versioned_docs/version-3.18-2/threat/suspicious-domains.mdx:52:1. From the web console, select **Threat Feeds** --> **Add Feed**.
./calico-enterprise_versioned_docs/version-3.18-2/threat/suspicious-domains.mdx:140:4. In the $[prodname] web console, go the “Alerts” page to view events that are generated when an endpoint in the cluster queries a name on the list.
./calico-enterprise_versioned_docs/version-3.18-2/threat/security-event-management.mdx:39:In the web console, go to **Threat defense**, **Security Events**.
./calico-enterprise_versioned_docs/version-3.18-2/threat/web-application-firewall.mdx:31:You simply enable WAF in the web console, and determine the services that you want to enable for WAF protection. By default WAF is set to `DetectionOnly` so no traffic will be denied until you are ready to turn on blocking mode.
./calico-enterprise_versioned_docs/version-3.18-2/threat/web-application-firewall.mdx:123:On the web console, click **Threat Defense**, **Web Application Firewall**, **Configure Web Application Firewall**.
./calico-enterprise_versioned_docs/version-3.18-2/threat/web-application-firewall.mdx:135:Alternatively, you can use the web console to apply WAF to the `frontend` service.
./calico-enterprise_versioned_docs/version-3.18-2/threat/web-application-firewall.mdx:143:1. On the web console, click **Threat Defense**, **Web Application Firewall**.
./calico-enterprise_versioned_docs/version-3.18-2/threat/deeppacketinspection.mdx:13:Security teams need to run DPI quickly in response to unusual network traffic in clusters so they can identify potential threats. Also, it is critical to run DPI on select workloads (not all) to efficiently make use of cluster resources and minimize the impact of false positives. $[prodname] provides an easy way to perform DPI using [Snort community rules](https://www.snort.org/downloads/#rule-downloads). You can disable DPI at any time, selectively configure for namespaces and endpoints, and alerts are generated in the Alerts dashboard in the web console.
./calico-enterprise_versioned_docs/version-3.18-2/threat/deeppacketinspection.mdx:17:For each deep packet inspection resource (DeepPacketInspection), $[prodname] creates a live network monitor that inspects the header and payload information of packets that match the Snort community rules. Whenever malicious activities are suspected, an alert is automatically added to the Alerts page in the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.18-2/threat/deeppacketinspection.mdx:102:The alerts generated by deep packet inspection are available in the web console in the Alerts page.
./calico-enterprise_versioned_docs/version-3.18-2/threat/tor-vpn-feed-and-dashboard.mdx:35:- Log in to the $[prodname] web console, and go to **kibana**, select **dashboard**, and select **Tor-VPN Dashboard**.
./calico-enterprise_versioned_docs/version-3.18-2/threat/tor-vpn-feed-and-dashboard.mdx:60:2. Now, you can monitor the Dashboard for any malicious activity. The dashboard can be found at the $[prodname] web console, go to "kibana" and then go to "Dashboard". Select "Tor-VPN Dashboard".
./calico-enterprise_versioned_docs/version-3.18-2/threat/suspicious-ips.mdx:53:#### Using the web console
./calico-enterprise_versioned_docs/version-3.18-2/threat/suspicious-ips.mdx:55:1. From the web console, select **Threat Feeds** --> **Add Feed**.
./calico-enterprise_versioned_docs/version-3.18-2/threat/suspicious-ips.mdx:66:> Go to the Alerts page to view events that are generated when an IP is displayed on the threat feed list. For more information, see [Manage alerts](../visibility/alerts.mdx). When you create a global threat feed in the web console, network traffic is not automatically blocked. If you find suspicious IPs on the Alerts page, you need to create a network policy to block the traffic. For help with policy, see [Block traffic to a cluster](#block-traffic-to-a-cluster).
./calico-enterprise_versioned_docs/version-3.18-2/threat/suspicious-ips.mdx:142:4. In the $[prodname] web console, go the “Alerts" page to view events that are generated when an IP is displayed on the threat feed list.
./calico-enterprise_versioned_docs/version-3.18-2/threat/suspicious-ips.mdx:233:Open the $[prodname] web console, and navigate to the “Alerts” page. If any of your pods have been communicating with the IP addresses in the FEODO tracker feed, you will see the results listed on this page. It is normal to not see any events listed on this page.
./calico-enterprise_versioned_docs/version-3.18-2/compliance/compliance-reports-cis.mdx:162: Upon completion, the report is available in the web console.
./calico-enterprise_versioned_docs/version-3.18-2/compliance/overview.mdx:193:Secure EE the web console.
./calico-enterprise_versioned_docs/version-3.18-2/compliance/overview.mdx:352: Upon completion, the report is available in the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.18-2/compliance/encrypt-cluster-pod-traffic.mdx:202:To view WireGuard statistics in the web console, you must enable them. From the left navbar, click **Dashboard**, and the Layout Settings icon.
./calico-enterprise_versioned_docs/version-3.18-2/compliance/encrypt-cluster-pod-traffic.mdx:208:When viewing WireGuard statistics, you might wonder why the charts in the web console Dashboard show more ingress traffic than egress if all the traffic goes within the cluster. The chart might show a 1% difference between traffic for the following reasons:
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/configure-identity-provider.mdx:12:Configure an external identity provider (IdP), create a user, and log in to the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/configure-identity-provider.mdx:39:- [Configure access to the web console](access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/configure-identity-provider.mdx:57: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/configure-identity-provider.mdx:128:1. Create values for some required variables. `MANAGER_URL` is the URL where the $[prodname] web console will be accessed,
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/configure-identity-provider.mdx:132: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/configure-identity-provider.mdx:165: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/configure-identity-provider.mdx:200: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/configure-identity-provider.mdx:256: **Problem**: Error: (502 bad gateway nginx) when logging in to the web console
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/configure-identity-provider.mdx:314:Most IdPs require redirect URIs to be allowed to redirect users at the end of the OAuth flow to the $[prodname] web console or to Kibana. Consult your IdP documentation for authorizing your domain for the respective origins and destinations.
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/configure-identity-provider.mdx:328:- If logging into Kibana fails with a `cookie not present` error, update the browser settings to allow third-party cookies, as the $[prodname] web console uses Kibana's cookies during login.
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:2:description: Configure access to the web console.
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:5:# Configure access to the web console
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:12:Configure access to the $[prodname] web console user interface.
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:16:For security, the $[prodname] web console is not exposed outside of the cluster by default. You can configure access to the $[prodname] web console using ingress, a load balancer service, or port forwarding.
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:27:| Kubernetes ingress | Configure your cluster with an ingress controller to implement the `Ingress` resource using [Kubernetes ingress](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer). | Ensure the $[prodname] web console receives a HTTPS (TLS) connection (not unencrypted HTTP). If you require TLS termination at your ingress, you must use a proxy that supports transparent HTTP/2 proxying, (for example, Envoy), or re-originate a TLS connection from your proxy to the $[prodname] web console. If you do not require TLS termination, configure your proxy to “pass thru” the TLS to the $[prodname] web console. |
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:28:| Load balancer | Configure your cluster with a service load balancer controller to implement the external load balancer. See [Kubernetes loadbalancer](https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/) | Ensure the $[prodname] web console receives a HTTPS (TLS) connection (not unencrypted HTTP). If you require TLS termination at your load balancer, you must use a load balancer that supports transparent HTTP/2 proxying, or re-originate a TLS connection from your load balancer to the $[prodname] web console. If you do not require TLS termination, configure your proxy to “pass thru” the TLS to the $[prodname] web console. |
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:29:| Port forwarding | Forward traffic from a local port to the Kubernetes API server, where it is proxied to the web console. This approach is **not recommended for production**, but is useful if you do not have a load balancer or ingress infrastructure configured, or you need to get started quickly. | n/a |
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:34:### Configure access to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:85:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:87:Access the $[prodname] web console in your browser at: `https://localhost:9443`
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:113:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:115:Access the $[prodname] web console in your browser at: `https://localhost:9443`
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:126:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:128:Access the $[prodname] web console in your browser at: `https://localhost:9443`
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:133:To expose the web console using OpenShift routes, create the following route with these required parameters:
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:161:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/access-the-manager.mdx:163:Access the $[prodname] web console in your browser using the URL with clustername. For example: `https://manager.apps.demo-ocp.tigera-solutions.io:9443`
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/index.mdx:2:description: Get started using the web console.
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/index.mdx:6:# The Calico Enterprise web console
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/authentication-quickstart.mdx:2:description: Use default token authentication to log in to the web console and Kibana.
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/authentication-quickstart.mdx:9:Get started quickly with our default token authentication to log in to the $[prodname] web console and Kibana.
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/authentication-quickstart.mdx:15:Token authentication is the default authentication option for the $[prodname] web console. When a service account is created, an
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/authentication-quickstart.mdx:17:account in to the web console and log in.
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/authentication-quickstart.mdx:23:- **the $[prodname] web console:** `https://<host>:<port>/login/token`.
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/authentication-quickstart.mdx:28:Make sure you have installed $[prodname] using one of the [installation guides](../../getting-started/index.mdx) and have set up [access to the web console](access-the-manager.mdx).
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/authentication-quickstart.mdx:38:**Log in to the $[prodname] web console**
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/authentication-quickstart.mdx:46:Give the service account permissions to access the $[prodname] web console, and a $[prodname] cluster role:
./calico-enterprise_versioned_docs/version-3.18-2/operations/cnx/roles-and-permissions.mdx:34:- Basic user with access to the $[prodname] web console and Kibana:
./calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/recommended-metrics.mdx:305:The following policy metrics are a separate endpoint exposed by Felix that are used in the web console. They require special Prometheus configuration to scrape the metrics. For details, see [Policy metrics](./policy-metrics).
./calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/policy-metrics.mdx:53:- the $[prodname] web console, also deployed as part of the $[prodname] manifest,
./calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/metrics/policy-metrics.mdx:108:Using these metrics, one can identify allow, and denied byte rate and packet rate, both inbound and outbound, indexed by both policy and rule. the $[prodname] web console Dashboard makes heavy usage of these metrics.
./calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/prometheus/byo-prometheus.mdx:32:With BYO Prometheus, $[prodname] metrics and alerts are not visible in the web console.
./calico-enterprise_versioned_docs/version-3.18-2/operations/monitor/prometheus/support.mdx:15:You install the $[prodname] Prometheus operator and CRDs during $[prodname] installation. $[prodname] metrics and alerts are available in the web console. You configure alerts through Prometheus AlertManager.
./calico-enterprise_versioned_docs/version-3.18-2/operations/index.mdx:11:## Configuring the web console
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/manager-tls.mdx:9:Provide TLS certificates that secure access to the $[prodname] web console user interface.
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/manager-tls.mdx:13:By default, the $[prodname] web console uses self-signed TLS certificates on connections. This article describes how to provide TLS certificates that users' browsers will trust.
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/manager-tls.mdx:17:- **Get the certificate and key pair for the $[prodname] web console**
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/manager-tls.mdx:18: Generate the certificate using any X.509-compatible tool or from your organization's Certificate Authority. The certificate must have Common Name or Subject Alternate Names that match the IPs or DNS names that will be used to [access the web console](../cnx/access-the-manager.mdx).
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/manager-tls.mdx:34:If the $[prodname] web console is already running then updating the secret should cause it to restart and pickup the new certificate and key. This will result in a short period of unavailability of the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/manager-tls.mdx:38:Additional documentation is available for securing [the $[prodname] web console connections](crypto-auth.mdx#calico-enterprise-manager-connections).
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:31:Tigera the $[prodname] web console's web interface, run from your browser, uses HTTPS to securely communicate
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:32:with the $[prodname] web console, which in turn, communicates with the Kubernetes and $[prodname] API
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:40:the $[prodname] web console through a
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:44:at the $[prodname] web console. This means that the TLS certificates used to secure traffic
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:45:between your web browser and the $[prodname] web console do not need to be shared or related
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:49:![the $[prodname] web console traffic diagram](/img/calico-enterprise/cnx-tls-mgr-comms.svg)
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:56:browser and the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:60:To properly configure TLS in the $[prodname] web console, you will need
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:69:matches the host name/DNS entry/IP address that is used to access the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:81: the certificates that the $[prodname] web console is using. This is generally caused by using
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:90: to be imported into every browser you access the $[prodname] web console from.
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:93: securely accessing the $[prodname] web console with TLS, you may want to make sure that the Common Name
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:95: entry/IP address that is used to access the $[prodname] web console (i.e. what it says in the browser
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:96: address bar). In Google Chrome you can check the $[prodname] web console certificate with Developer Tools
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:99: Subject Alternative Name and reconfigure the $[prodname] web console following the steps above.
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:104:proxies etc., between user web browsers and the $[prodname] web console. If you do so, configure your proxy
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:105:such that the $[prodname] web console receives a HTTPS (TLS) connection, not unencrypted HTTP.
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:110:- re-originate a TLS connection from your proxy to the $[prodname] web console, as it expects TLS
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/crypto-auth.mdx:112:If you do not require TLS termination, configure your proxy to "pass thru" the TLS to the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/apiserver-tls.mdx:32:To provide certificates for use during deployment you must create a secret before applying the 'custom-resource.yaml' or before creating the Installation resource. To specify certificates for use in the $[prodname] web console, create a secret using the following command:
./calico-enterprise_versioned_docs/version-3.18-2/operations/comms/apiserver-tls.mdx:52:Additional documentation is available for securing [the $[prodname] web console connections](crypto-auth.mdx#connections-from-calico-enterprise-components-to-kube-apiserver-kubernetes-and-openshift).
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/install-on-clusters/docker-enterprise.mdx:131:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/install-on-clusters/rancher.mdx:128:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/install-on-clusters/windows-calico/manual-install/openshift-installation.mdx:57:- [Configure access to the $[prodname] web console](../../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/install-on-clusters/tkg.mdx:51:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/install-on-clusters/rancher-ui.mdx:110:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/install-on-clusters/openshift/installation.mdx:37:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/install-on-clusters/aks.mdx:83:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/install-on-clusters/rke2.mdx:125:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/install-on-clusters/eks.mdx:53:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/install-on-clusters/gke.mdx:65:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/install-on-clusters/kubernetes/helm.mdx:128:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx:43:- [Log in to the $[prodname] web console](#log-in-to-calico-enterprise-manager)
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx:158:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/install-on-clusters/kubernetes/options-install.mdx:35:| **Manager** | Installs the $[prodname] web console web UI. |
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/install-on-clusters/kubernetes/generic-install.mdx:43:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx:29:are the dashboards in the web console. Data ingestion is temporarily paused and will continue when the LogStorage is
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/operator.mdx:42:are the dashboards in the web console. Data ingestion is temporarily paused and will continue when the LogStorage is
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx:43:that depend on LogStorage are temporarily unavailable, including dashboards in the web console. Data ingestion is paused
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx:89:- [Configure access to the $[prodname] web console](../../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/standard.mdx:100:- [Configure access to the $[prodname] web console](../../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx:149: To access resources belonging to a managed cluster from the $[prodname] web console, the service or user account used to log in must have appropriate permissions defined in the managed cluster.
./calico-enterprise_versioned_docs/version-3.18-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx:151:Define admin-level permissions for the service account `mcm-user` we created to log in to the web console. Run the following command against your managed cluster.
./calico-enterprise_versioned_docs/version-3.18-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx:163:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx:273:To access resources in a managed cluster from the $[prodname] web console within the management cluster, the logged-in user must have appropriate permissions defined in that managed cluster (clusterrole bindings).
./calico-enterprise_versioned_docs/version-3.18-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx:291:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.18-2/multicluster/set-up-multi-cluster-management/standard-install/create-a-management-cluster.mdx:70:To access resources in a managed cluster from the $[prodname] web console within the management cluster, the logged-in user must have appropriate permissions defined in that managed cluster (clusterrole bindings).
./calico-enterprise_versioned_docs/version-3.18-2/multicluster/fine-tune-deployment.mdx:30:- Maps to port 9449 on the Manager (web console) pod
./calico-enterprise_versioned_docs/version-3.18-2/multicluster/fine-tune-deployment.mdx:70:- All users that log in to the $[prodname] web console must use a valid service account or user account in the management cluster.
./calico-enterprise_versioned_docs/version-3.18-2/multicluster/fine-tune-deployment.mdx:83:A standalone cluster uses the cluster name cluster for Elasticsearch indexes. This is also the name used by a management cluster. For a managed cluster, its cluster name is the value chosen by the user at the time of registration, through the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.18-2/multicluster/fine-tune-deployment.mdx:131:1. Log in to the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.18-2/reference/resources/globalalert.mdx:9:added to the Alerts page in the $[prodname] web console. Alerts may
./calico-enterprise_versioned_docs/version-3.18-2/reference/resources/globalalert.mdx:224:alerts in the $[prodname] web console Alert user interface. Any field
./calico-enterprise_versioned_docs/version-3.18-2/reference/resources/globalalert.mdx:274:These are used in the $[prodname] web console to create alerts
./calico-enterprise_versioned_docs/version-3.18-2/reference/resources/deeppacketinspection.mdx:11:the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.18-2/reference/resources/policyrecommendations.mdx:21:The policy recommendation scope is a collection of configuration options to control [policy recommendation](../../network-policy/recommendations/policy-recommendations.mdx) in the web console.
./calico-enterprise_versioned_docs/version-3.18-2/reference/resources/alertexception.mdx:7:An alert exception resource is a filter that hides specific alerts from users in the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.18-2/reference/resources/alertexception.mdx:8:You can filter alerts by time range or indefinitely. If an alert exception expires, alerts will reappear in the web console.
./calico-enterprise_versioned_docs/version-3.18-2/reference/resources/alertexception.mdx:40:| selector | Selects alerts to filter from the $[prodname] web console queries. | string | yes | [selector](#selector) |
./calico-enterprise_versioned_docs/version-3.18-2/reference/installation/_api.mdx:12372:When set to manager-tls, voltron will use the same cert bundle that the web console is served with.
./calico-enterprise_versioned_docs/version-3.18-2/reference/architecture/overview.mdx:129:**Main task**: Retrieves capture files (pcap format) generated by a packet capture for use with network protocol analysis tools like Wireshark. The packet capture feature is installed by default in all cluster types. Packet capture data is visible in the web console, service graph.
./calico-enterprise_versioned_docs/version-3.20-2/_includes/content/_default-install.mdx:6:| User interface | the $[prodname] web console user interface (with a default of “no access outside the cluster”). |
./calico-enterprise_versioned_docs/version-3.20-2/_includes/content/_license.mdx:9:### Does the web console display license expiration?
./calico-enterprise_versioned_docs/version-3.20-2/_includes/content/_license.mdx:11:Yes. The license indicator in the web console (top right banner) turns red when the license expires.
./calico-enterprise_versioned_docs/version-3.20-2/_includes/content/_license.mdx:19:Although users can still log in to the web console, your deployment is no longer operational. All policy enforcement stops, except for policies in the default tier. In most cases, you will experience broken connectivity (depending on your policies in the default tier). $[prodname] stops reporting flow logs, DNS logs, and $[prodname] metrics, which affects other UI elements like Service Graph and dashboards. Although some elements may appear to work, actions are not saved, and you should regard your deployment as non-functional. We recommend that you proactively manage your license to avoid disruption.
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/application-layer-policies/alp-tutorial.mdx:86:is that you'll see HTTP traffic flows in the web console in features like Service Graph.
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/policy-firewalls/fortinet-integration/overview.mdx:33:**Solution**: Use FortiManager to create firewall policies that are applied as $[prodname] network policies on Kubernetes workloads. Use the power of a $[prodname] “higher-order tier” so Kubernetes policy is evaluated early in the policy processing order, but update policy using FortiManager UI. Use the $[prodname] web console as a secondary interface to verify the integration and troubleshoot using logs.
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:29:1. Use the $[prodname] web console to verify the integration, and then FortiManager UI to make all updates to policy rules.
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:47:- Login access to [the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:65:Create a [$[prodname] tier](../../policy-tiers/tiered-policy.mdx) in the $[prodname] web console for each Kubernetes cluster you want to secure. We recommend that you create a new tier (rather than reusing an existing tier) for all global network policies created by the $[prodname] integration controller.
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:110: | tier | Tier name you created in the web console |
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:154:5. Log in to the $[prodname] web console, and under the tier that you specified in the ConfigMap, verify that the GlobalNetworkPolicies are created.
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/policy-tiers/tiered-policy.mdx:29:To create a tier and policy in the web console:
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/policy-tiers/policy-tutorial-ui.mdx:9:- How to create a policy in the web console
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/policy-tiers/policy-tutorial-ui.mdx:32:To follow along in the web console, click **Policies**.
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/policy-tiers/rbac-tiered-policies.mdx:26:In $[prodname], global network policy and network policy resources are associated with a specific tier. Admins can configure access control for these $[prodname] policies using standard Kubernetes `Role` and `ClusterRole` resource types. This makes it easy to manage RBAC for both Kubernetes network policies and $[prodname] tiered network policies. RBAC permissions include managing resources using the $[prodname] web console, and `kubectl`.
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/policy-tiers/rbac-tiered-policies.mdx:90:Create an Admin user with full access to the $[prodname] web console (as well as everything else in the cluster) using the following command. See the Kubernetes documentation to identify users based on your chosen [authentication method](https://kubernetes.io/docs/reference/access-authn-authz/authentication/), and how to use the [RBAC resources](https://kubernetes.io/docs/reference/access-authn-authz/rbac/).
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/policy-tiers/rbac-tiered-policies.mdx:100:All users using the $[prodname] web console should be able to create authorizationreviews and authorizationrequests as well as access
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/policy-tiers/rbac-tiered-policies.mdx:373:tier. This has the effect of making the **net-sec** tier visible in the $[prodname] web console (including listing the names of the policies it contains).
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/policy-best-practices.mdx:329:A big obstacle to adopting Kubernetes is not having confidence that you can effectively prevent, detect, and mitigate across diverse teams. The following policy life cycle tools in the web console (**Policies** tab) can help.
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/recommendations/learn-about-policy-recommendations.mdx:31:1. In the web console left navbar, click the **Policies** icon.
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/recommendations/learn-about-policy-recommendations.mdx:96:1. In the web console left navbar, click **Service Graph**.
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/recommendations/policy-recommendations.mdx:37:Basic knowledge of policies in the web console and tiers:
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/recommendations/policy-recommendations.mdx:43:Creating and managing policy recommendations is available only in the web console.
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/recommendations/policy-recommendations.mdx:55:### Enable policy recommendations **using the web console**
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/recommendations/policy-recommendations.mdx:57:1. In the left navbar in the web console, click **Policies**, **Recommendations**.
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/beginners/calico-labels.mdx:118:$[prodname] labels must be used with the correct selector or the policy will not work as designed (and there are no error messages in the web console or when applying the YAML).
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/beginners/simple-policy-cnx.mdx:161: Alternatively, you may also use the $[prodname] web console to inspect and view information and metrics associated with policies, endpoints, and nodes.
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/beginners/simple-policy-cnx.mdx:218:In the $[prodname] web console, head to the dashboard view. You will see graphs associated with allowed packets/bytes and denied packets/bytes. The graphs represent the rates at which packets/bytes are being allowed or denied and are time windowed.
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/networksets.mdx:21:If you are familiar with Service Graph in the web console, you know the value of seeing pod-to-pod traffic within your cluster. But what about traffic external to your cluster?
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/networksets.mdx:53:In this section, we’ll walk through how to create a namespaced network set in the web console. You can follow along using your cluster or tigera-labs cluster.
./calico-enterprise_versioned_docs/version-3.20-2/network-policy/policy-impact-preview.mdx:23:1. From the Edit Policy page on the web console, modify any attribute of the policy.
./calico-enterprise_versioned_docs/version-3.20-2/visibility/alerts.mdx:18:You can manage alerts and alert events in the web console, or using the CLI. $[prodname] also provides alert templates
./calico-enterprise_versioned_docs/version-3.20-2/visibility/alerts.mdx:31:- [Manage alerts in the web console](#manage-alerts-in-manager-ui)
./calico-enterprise_versioned_docs/version-3.20-2/visibility/alerts.mdx:34:### Manage alerts in the web console
./calico-enterprise_versioned_docs/version-3.20-2/visibility/alerts.mdx:36:You can view alert events in the web console in several places: the **Alerts** page, **Service Graph**, and the **Kibana** dashboard.
./calico-enterprise_versioned_docs/version-3.20-2/visibility/alerts.mdx:115:1. In the web console, go to the **Alerts** page to view alert events.
./calico-enterprise_versioned_docs/version-3.20-2/visibility/packetcapture.mdx:13:$[prodname] packet capture is implemented in a Kubernetes-native way so you can troubleshoot service/application connectivity issues and performance issues. You can start a packet capture in the web console Service Graph, or using the CLI.
./calico-enterprise_versioned_docs/version-3.20-2/visibility/packetcapture.mdx:72:##### Enable packet capture using the web console
./calico-enterprise_versioned_docs/version-3.20-2/visibility/packetcapture.mdx:74:1. From the web console, click the Service Graph to view the service graph diagram for your cluster.
./calico-enterprise_versioned_docs/version-3.20-2/visibility/kube-audit.mdx:28:### Audit logs in the web console
./calico-enterprise_versioned_docs/version-3.20-2/visibility/kube-audit.mdx:30:Like $[prodname] audit logs, Kubernetes audit logs are displayed in the web console in the Timeline dashboard, Kibana dashboard (indexed by, `tigera_secure_ee_audit_kube`), and provide the core data for compliance reports.
./calico-enterprise_versioned_docs/version-3.20-2/visibility/kibana.mdx:24:In the web console, from the left navbar select, **Kibana**. A new browser tab opens into Kibana.
./calico-enterprise_versioned_docs/version-3.20-2/visibility/elastic/audit-overview.mdx:27:### Audit logs in the web console
./calico-enterprise_versioned_docs/version-3.20-2/visibility/elastic/audit-overview.mdx:29:$[prodname] audit logs are displayed in the Timeline dashboard in the web console. You can filter logs, and export data in .json or .yaml formats.
./calico-enterprise_versioned_docs/version-3.20-2/visibility/elastic/rbac-elasticsearch.mdx:19:Elasticsearch resources are associated with the **Kubernetes API group**, `lma.tigera.io`. You can grant access to resources per cluster. The default cluster name for $[prodname] is, `cluster`. As shown in the following table, each Elasticsearch resource is mapped to a specific RBAC resource name within the `lma.tigera.io` API group. In the $[prodname] web console, Elasticsearch resources are called, **indexes or indices**.
./calico-enterprise_versioned_docs/version-3.20-2/visibility/elastic/rbac-elasticsearch.mdx:42:- A `tigera-network-admin` role with full permissions to create and modify resources. For help, see [Log in to the $[prodname] web console](../../operations/cnx/authentication-quickstart.mdx).
./calico-enterprise_versioned_docs/version-3.20-2/visibility/elastic/rbac-elasticsearch.mdx:44:- To view Elasticsearch resources in the $[prodname] web console, users must have [minimum permissions](../../network-policy/policy-tiers/rbac-tiered-policies.mdx).
./calico-enterprise_versioned_docs/version-3.20-2/visibility/elastic/overview.mdx:17:- View Elasticsearch logs in the $[prodname] web console (Kibana dashboard and Flow Visualizer), and the [Elasticsearch API](https://www.elastic.co/guide/en/elasticsearch/reference/current/search.html)
./calico-enterprise_versioned_docs/version-3.20-2/visibility/elastic/index.mdx:2:description: Configure logs for visibility in the web console.
./calico-enterprise_versioned_docs/version-3.20-2/visibility/elastic/troubleshoot.mdx:52:Be aware that removing LogStorage temporarily removes Elasticsearch from your cluster. Features that depend on LogStorage are temporarily unavailable, including the dashboards in the web console. Data ingestion is also temporarily paused, but will resume when the LogStorage is up and running again.
./calico-enterprise_versioned_docs/version-3.20-2/visibility/elastic/l7/configure.mdx:29:L7 logs are visible in the web console, service graph, in the HTTP tab.
./calico-enterprise_versioned_docs/version-3.20-2/visibility/elastic/l7/configure.mdx:123:## View L7 logs in the web console
./calico-enterprise_versioned_docs/version-3.20-2/visibility/elastic/l7/configure.mdx:129:1. In the web console left navbar, click **Service Graph**.
./calico-enterprise_versioned_docs/version-3.20-2/visibility/elastic/l7/configure.mdx:138:1. In the web console left navbar, click **Kibana**.
./calico-enterprise_versioned_docs/version-3.20-2/visibility/get-started-cem.mdx:2:description: Tour the main features of the web console.
./calico-enterprise_versioned_docs/version-3.20-2/visibility/get-started-cem.mdx:12:Let's go through each item in the web console left navbar from top to bottom. You can follow along using any cluster.
./calico-enterprise_versioned_docs/version-3.20-2/visibility/get-started-cem.mdx:110:This page is where you switch views between clusters in the web console. When you connect to a different cluster, the entire web console view changes to reflect the selected cluster.
./calico-enterprise_versioned_docs/version-3.20-2/networking/egress/troubleshoot.mdx:220:In [the web console](../../visibility/get-started-cem.mdx), check for dropped packets because of policy on the outbound connection path. If you are using the iptables data plane, you can also run the following command on the client and gateway nodes to look at a lower level.
./calico-enterprise_versioned_docs/version-3.20-2/networking/configuring/multiple-networks.mdx:67:- [Install and configure calicoctl](../../operations/clis/calicoctl/index.mdx) or configure access to [the web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/networking/configuring/multiple-networks.mdx:198:**In the $[prodname] web console**, go to the **WorkloadEndpoint** page to see all of the WorkloadEndpoints, including the network labels are for targeting WorkloadEndpoints with policy.
./calico-enterprise_versioned_docs/version-3.20-2/threat/configuring-webhooks.mdx:25:1. In the web console, select **Activity** > **Webhooks**, and then click **Create your first webhook**.
./calico-enterprise_versioned_docs/version-3.20-2/threat/suspicious-domains.mdx:50:#### Using the web console
./calico-enterprise_versioned_docs/version-3.20-2/threat/suspicious-domains.mdx:52:1. From the web console, select **Threat Feeds** --> **Add Feed**.
./calico-enterprise_versioned_docs/version-3.20-2/threat/suspicious-domains.mdx:140:4. In the $[prodname] web console, go the “Security Events” page to view events that are generated when an endpoint in the cluster queries a name on the list.
./calico-enterprise_versioned_docs/version-3.20-2/threat/security-event-management.mdx:31:In the web console, go to **Threat defense**, **Security Events**.
./calico-enterprise_versioned_docs/version-3.20-2/threat/web-application-firewall.mdx:30:You simply enable WAF in the web console, and determine the deployments that you want to enable for WAF protection. By default WAF is set to `DetectionOnly` so no traffic will be denied until you are ready to turn on blocking mode.
./calico-enterprise_versioned_docs/version-3.20-2/threat/web-application-firewall.mdx:81:Or, in the web console, click **Threat Defense > Web Application Firewall > Configure Web Application Firewall**.
./calico-enterprise_versioned_docs/version-3.20-2/threat/web-application-firewall.mdx:104:Alternatively, you can use the web console to apply WAF to the `frontend` deployment if you opted for sidecars.
./calico-enterprise_versioned_docs/version-3.20-2/threat/web-application-firewall.mdx:112:1. On the web console, click **Threat Defense**, **Web Application Firewall**.
./calico-enterprise_versioned_docs/version-3.20-2/threat/deeppacketinspection.mdx:16:You can disable DPI at any time, selectively configure for namespaces and endpoints, and alerts are generated in the Alerts dashboard in the web console.
./calico-enterprise_versioned_docs/version-3.20-2/threat/deeppacketinspection.mdx:21:Whenever malicious activities are suspected, an alert is automatically added to the Security Events page in the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-2/threat/deeppacketinspection.mdx:107:The alerts generated by deep packet inspection are available in the web console in the Alerts page.
./calico-enterprise_versioned_docs/version-3.20-2/threat/tor-vpn-feed-and-dashboard.mdx:35:- Log in to the $[prodname] web console, and go to **kibana**, select **dashboard**, and select **Tor-VPN Dashboard**.
./calico-enterprise_versioned_docs/version-3.20-2/threat/tor-vpn-feed-and-dashboard.mdx:60:2. Now, you can monitor the Dashboard for any malicious activity. The dashboard can be found at the $[prodname] web console, go to "kibana" and then go to "Dashboard". Select "Tor-VPN Dashboard".
./calico-enterprise_versioned_docs/version-3.20-2/threat/suspicious-ips.mdx:53:#### Using the web console
./calico-enterprise_versioned_docs/version-3.20-2/threat/suspicious-ips.mdx:55:1. From the web console, select **Threat Feeds** --> **Add Feed**.
./calico-enterprise_versioned_docs/version-3.20-2/threat/suspicious-ips.mdx:66:> Go to the Security Events page to view events that are generated when an IP is displayed on the threat feed list. For more information, see [Manage alerts](../visibility/alerts.mdx). When you create a global threat feed in the web console, network traffic is not automatically blocked. If you find suspicious IPs on the Security Events page, you need to create a network policy to block the traffic. For help with policy, see [Block traffic to a cluster](#block-traffic-to-a-cluster).
./calico-enterprise_versioned_docs/version-3.20-2/threat/suspicious-ips.mdx:142:4. In the $[prodname] web console, go the “Security Events" page to view events that are generated when an IP is displayed on the threat feed list.
./calico-enterprise_versioned_docs/version-3.20-2/threat/suspicious-ips.mdx:233:Open the $[prodname] web console, and navigate to the “Security Events” page. If any of your pods have been communicating with the IP addresses in the FEODO tracker feed, you will see the results listed on this page. It is normal to not see any events listed on this page.
./calico-enterprise_versioned_docs/version-3.20-2/release-notes/index.mdx:50:* Enhanced filtering options in the endpoints page of the web console.
./calico-enterprise_versioned_docs/version-3.20-2/release-notes/index.mdx:199:* Fixes an issue where the web console reports "Invalid value" when editing and saving staged policies.
./calico-enterprise_versioned_docs/version-3.20-2/compliance/compliance-reports-cis.mdx:173: Upon completion, the report is available in the web console.
./calico-enterprise_versioned_docs/version-3.20-2/compliance/overview.mdx:202:Secure EE the web console.
./calico-enterprise_versioned_docs/version-3.20-2/compliance/overview.mdx:361: Upon completion, the report is available in the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-2/compliance/encrypt-cluster-pod-traffic.mdx:202:To view WireGuard statistics in the web console, you must enable them. From the left navbar, click **Dashboard**, and the Layout Settings icon.
./calico-enterprise_versioned_docs/version-3.20-2/compliance/encrypt-cluster-pod-traffic.mdx:208:When viewing WireGuard statistics, you might wonder why the charts in the web console Dashboard show more ingress traffic than egress if all the traffic goes within the cluster. The chart might show a 1% difference between traffic for the following reasons:
./calico-enterprise_versioned_docs/version-3.20-2/compliance/enable-compliance.mdx:45:### Enable compliance reports using the web console
./calico-enterprise_versioned_docs/version-3.20-2/compliance/enable-compliance.mdx:47:On the web console, click **Compliance Reports**, **Enable Compliance Reports**.
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/configure-identity-provider.mdx:12:Configure an external identity provider (IdP), create a user, and log in to the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/configure-identity-provider.mdx:39:- [Configure access to the web console](access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/configure-identity-provider.mdx:57: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/configure-identity-provider.mdx:128:1. Create values for some required variables. `MANAGER_URL` is the URL where the $[prodname] web console will be accessed,
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/configure-identity-provider.mdx:132: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/configure-identity-provider.mdx:165: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/configure-identity-provider.mdx:200: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/configure-identity-provider.mdx:256: **Problem**: Error: (502 bad gateway nginx) when logging in to the web console
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/configure-identity-provider.mdx:314:Most IdPs require redirect URIs to be allowed to redirect users at the end of the OAuth flow to the $[prodname] web console or to Kibana. Consult your IdP documentation for authorizing your domain for the respective origins and destinations.
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/configure-identity-provider.mdx:328:- If logging into Kibana fails with a `cookie not present` error, update the browser settings to allow third-party cookies, as the $[prodname] web console uses Kibana's cookies during login.
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:2:description: Configure access to the web console.
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:5:# Configure access to the web console
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:12:Configure access to the $[prodname] web console user interface.
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:16:For security, the $[prodname] web console is not exposed outside of the cluster by default. You can configure access to the $[prodname] web console using ingress, a load balancer service, or port forwarding.
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:27:| Kubernetes ingress | Configure your cluster with an ingress controller to implement the `Ingress` resource using [Kubernetes ingress](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer). | Ensure the $[prodname] web console receives a HTTPS (TLS) connection (not unencrypted HTTP). If you require TLS termination at your ingress, you must use a proxy that supports transparent HTTP/2 proxying, (for example, Envoy), or re-originate a TLS connection from your proxy to the $[prodname] web console. If you do not require TLS termination, configure your proxy to “pass thru” the TLS to the $[prodname] web console. |
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:28:| Load balancer | Configure your cluster with a service load balancer controller to implement the external load balancer. See [Kubernetes loadbalancer](https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/) | Ensure the $[prodname] web console receives a HTTPS (TLS) connection (not unencrypted HTTP). If you require TLS termination at your load balancer, you must use a load balancer that supports transparent HTTP/2 proxying, or re-originate a TLS connection from your load balancer to the $[prodname] web console. If you do not require TLS termination, configure your proxy to “pass thru” the TLS to the $[prodname] web console. |
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:29:| Port forwarding | Forward traffic from a local port to the Kubernetes API server, where it is proxied to the web console. This approach is **not recommended for production**, but is useful if you do not have a load balancer or ingress infrastructure configured, or you need to get started quickly. | n/a |
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:34:### Configure access to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:85:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:87:Access the $[prodname] web console in your browser at: `https://localhost:9443`
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:113:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:115:Access the $[prodname] web console in your browser at: `https://localhost:9443`
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:126:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:128:Access the $[prodname] web console in your browser at: `https://localhost:9443`
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:133:To expose the web console using OpenShift routes, create the following route with these required parameters:
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:161:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/access-the-manager.mdx:163:Access the $[prodname] web console in your browser using the URL with clustername. For example: `https://manager.apps.demo-ocp.tigera-solutions.io:9443`
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/index.mdx:2:description: Get started using the web console.
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/index.mdx:6:# The Calico Enterprise web console
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/authentication-quickstart.mdx:2:description: Use default token authentication to log in to the web console and Kibana.
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/authentication-quickstart.mdx:9:Get started quickly with our default token authentication to log in to the $[prodname] web console and Kibana.
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/authentication-quickstart.mdx:15:Token authentication is the default authentication option for the $[prodname] web console. When a service account is created, an
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/authentication-quickstart.mdx:17:account in to the web console and log in.
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/authentication-quickstart.mdx:23:- **the $[prodname] web console:** `https://<host>:<port>/login/token`.
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/authentication-quickstart.mdx:28:Make sure you have installed $[prodname] using one of the [installation guides](../../getting-started/index.mdx) and have set up [access to the web console](access-the-manager.mdx).
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/authentication-quickstart.mdx:38:**Log in to the $[prodname] web console**
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/authentication-quickstart.mdx:46:Give the service account permissions to access the $[prodname] web console, and a $[prodname] cluster role:
./calico-enterprise_versioned_docs/version-3.20-2/operations/cnx/roles-and-permissions.mdx:34:- Basic user with access to the $[prodname] web console and Kibana:
./calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/recommended-metrics.mdx:305:The following policy metrics are a separate endpoint exposed by Felix that are used in the web console. They require special Prometheus configuration to scrape the metrics. For details, see [Policy metrics](./policy-metrics).
./calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/policy-metrics.mdx:53:- the $[prodname] web console, also deployed as part of the $[prodname] manifest,
./calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/metrics/policy-metrics.mdx:108:Using these metrics, one can identify allow, and denied byte rate and packet rate, both inbound and outbound, indexed by both policy and rule. the $[prodname] web console Dashboard makes heavy usage of these metrics.
./calico-enterprise_versioned_docs/version-3.20-2/operations/monitor/prometheus/support.mdx:15:You install the $[prodname] Prometheus operator and CRDs during $[prodname] installation. $[prodname] metrics and alerts are available in the web console. You configure alerts through Prometheus AlertManager.
./calico-enterprise_versioned_docs/version-3.20-2/operations/index.mdx:11:## Configuring the web console
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/manager-tls.mdx:9:Provide TLS certificates that secure access to the $[prodname] web console user interface.
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/manager-tls.mdx:13:By default, the $[prodname] web console uses self-signed TLS certificates on connections. This article describes how to provide TLS certificates that users' browsers will trust.
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/manager-tls.mdx:17:- **Get the certificate and key pair for the $[prodname] web console**
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/manager-tls.mdx:18: Generate the certificate using any X.509-compatible tool or from your organization's Certificate Authority. The certificate must have Common Name or Subject Alternate Names that match the IPs or DNS names that will be used to [access the web console](../cnx/access-the-manager.mdx).
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/manager-tls.mdx:34:If the $[prodname] web console is already running then updating the secret should cause it to restart and pickup the new certificate and key. This will result in a short period of unavailability of the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/manager-tls.mdx:38:Additional documentation is available for securing [the $[prodname] web console connections](crypto-auth.mdx#calico-enterprise-manager-connections).
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:31:Tigera the $[prodname] web console's web interface, run from your browser, uses HTTPS to securely communicate
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:32:with the $[prodname] web console, which in turn, communicates with the Kubernetes and $[prodname] API
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:40:the $[prodname] web console through a
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:44:at the $[prodname] web console. This means that the TLS certificates used to secure traffic
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:45:between your web browser and the $[prodname] web console do not need to be shared or related
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:49:![the $[prodname] web console traffic diagram](/img/calico-enterprise/cnx-tls-mgr-comms.svg)
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:56:browser and the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:60:To properly configure TLS in the $[prodname] web console, you will need
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:69:matches the host name/DNS entry/IP address that is used to access the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:81: the certificates that the $[prodname] web console is using. This is generally caused by using
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:90: to be imported into every browser you access the $[prodname] web console from.
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:93: securely accessing the $[prodname] web console with TLS, you may want to make sure that the Common Name
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:95: entry/IP address that is used to access the $[prodname] web console (i.e. what it says in the browser
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:96: address bar). In Google Chrome you can check the $[prodname] web console certificate with Developer Tools
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:99: Subject Alternative Name and reconfigure the $[prodname] web console following the steps above.
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:104:proxies etc., between user web browsers and the $[prodname] web console. If you do so, configure your proxy
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:105:such that the $[prodname] web console receives a HTTPS (TLS) connection, not unencrypted HTTP.
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:110:- re-originate a TLS connection from your proxy to the $[prodname] web console, as it expects TLS
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/crypto-auth.mdx:112:If you do not require TLS termination, configure your proxy to "pass thru" the TLS to the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/apiserver-tls.mdx:32:To provide certificates for use during deployment you must create a secret before applying the 'custom-resource.yaml' or before creating the Installation resource. To specify certificates for use in the $[prodname] web console, create a secret using the following command:
./calico-enterprise_versioned_docs/version-3.20-2/operations/comms/apiserver-tls.mdx:52:Additional documentation is available for securing [the $[prodname] web console connections](crypto-auth.mdx#connections-from-calico-enterprise-components-to-kube-apiserver-kubernetes-and-openshift).
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/docker-enterprise.mdx:121:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rancher.mdx:118:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/windows-calico/manual-install/openshift-installation.mdx:57:- [Configure access to the $[prodname] web console](../../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/tkg.mdx:51:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rancher-ui.mdx:110:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/openshift/hostedcontrolplanes.mdx:192:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/openshift/installation.mdx:37:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/aks.mdx:83:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/rke2.mdx:115:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/eks.mdx:53:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/gke.mdx:65:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/helm.mdx:140:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx:43:- [Log in to the $[prodname] web console](#log-in-to-calico-enterprise-manager)
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx:154:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/options-install.mdx:34:| **Manager** | Installs the $[prodname] web console web UI. |
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/install-on-clusters/kubernetes/generic-install.mdx:43:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/bare-metal/about.mdx:93:1. Follow [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx) page to configure the $[prodname] web console access.
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx:29:are the dashboards in the web console. Data ingestion is temporarily paused and will continue when the LogStorage is
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/operator.mdx:42:are the dashboards in the web console. Data ingestion is temporarily paused and will continue when the LogStorage is
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx:43:that depend on LogStorage are temporarily unavailable, including dashboards in the web console. Data ingestion is paused
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx:89:- [Configure access to the $[prodname] web console](../../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/standard.mdx:100:- [Configure access to the $[prodname] web console](../../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx:148: To access resources belonging to a managed cluster from the $[prodname] web console, the service or user account used to log in must have appropriate permissions defined in the managed cluster.
./calico-enterprise_versioned_docs/version-3.20-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx:150:Define admin-level permissions for the service account `mcm-user` we created to log in to the web console. Run the following command against your managed cluster.
./calico-enterprise_versioned_docs/version-3.20-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx:162:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx:272:To access resources in a managed cluster from the $[prodname] web console within the management cluster, the logged-in user must have appropriate permissions defined in that managed cluster (clusterrole bindings).
./calico-enterprise_versioned_docs/version-3.20-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx:290:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-2/multicluster/set-up-multi-cluster-management/standard-install/create-a-management-cluster.mdx:70:To access resources in a managed cluster from the $[prodname] web console within the management cluster, the logged-in user must have appropriate permissions defined in that managed cluster (clusterrole bindings).
./calico-enterprise_versioned_docs/version-3.20-2/multicluster/fine-tune-deployment.mdx:30:- Maps to port 9449 on the Manager (web console) pod
./calico-enterprise_versioned_docs/version-3.20-2/multicluster/fine-tune-deployment.mdx:70:- All users that log in to the $[prodname] web console must use a valid service account or user account in the management cluster.
./calico-enterprise_versioned_docs/version-3.20-2/multicluster/fine-tune-deployment.mdx:83:A standalone cluster uses the cluster name cluster for Elasticsearch indexes. This is also the name used by a management cluster. For a managed cluster, its cluster name is the value chosen by the user at the time of registration, through the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-2/multicluster/fine-tune-deployment.mdx:131:1. Log in to the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-2/reference/resources/globalalert.mdx:9:added to the Alerts page in the $[prodname] web console. Alerts may
./calico-enterprise_versioned_docs/version-3.20-2/reference/resources/globalalert.mdx:224:alerts in the $[prodname] web console Alert user interface. Any field
./calico-enterprise_versioned_docs/version-3.20-2/reference/resources/globalalert.mdx:274:These are used in the $[prodname] web console to create alerts
./calico-enterprise_versioned_docs/version-3.20-2/reference/resources/deeppacketinspection.mdx:11:the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-2/reference/resources/policyrecommendations.mdx:21:The policy recommendation scope is a collection of configuration options to control [policy recommendation](../../network-policy/recommendations/policy-recommendations.mdx) in the web console.
./calico-enterprise_versioned_docs/version-3.20-2/reference/resources/alertexception.mdx:7:An alert exception resource is a filter that hides specific alerts from users in the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-2/reference/resources/alertexception.mdx:8:You can filter alerts by time range or indefinitely. If an alert exception expires, alerts will reappear in the web console.
./calico-enterprise_versioned_docs/version-3.20-2/reference/resources/alertexception.mdx:40:| selector | Selects alerts to filter from the $[prodname] web console queries. | string | yes | [selector](#selector) |
./calico-enterprise_versioned_docs/version-3.20-2/reference/installation/_api.mdx:20324:When set to manager-tls, voltron will use the same cert bundle that the web console is served with.
./calico-enterprise_versioned_docs/version-3.20-2/reference/architecture/overview.mdx:129:**Main task**: Retrieves capture files (pcap format) generated by a packet capture for use with network protocol analysis tools like Wireshark. The packet capture feature is installed by default in all cluster types. Packet capture data is visible in the web console, service graph.
./calico-enterprise_versioned_docs/version-3.17/_includes/content/_default-install.mdx:6:| User interface | the $[prodname] web console user interface (with a default of “no access outside the cluster”). |
./calico-enterprise_versioned_docs/version-3.17/_includes/content/_license.mdx:9:### Does the web console display license expiration?
./calico-enterprise_versioned_docs/version-3.17/_includes/content/_license.mdx:11:Yes. The license indicator in the web console (top right banner) turns red when the license expires.
./calico-enterprise_versioned_docs/version-3.17/_includes/content/_license.mdx:19:Although users can still log in to the web console, your deployment is no longer operational. All policy enforcement stops, except for policies in the default tier. In most cases, you will experience broken connectivity (depending on your policies in the default tier). $[prodname] stops reporting flow logs, DNS logs, and $[prodname] metrics, which affects other UI elements like Service Graph and dashboards. Although some elements may appear to work, actions are not saved, and you should regard your deployment as non-functional. We recommend that you proactively manage your license to avoid disruption.
./calico-enterprise_versioned_docs/version-3.17/network-policy/application-layer-policies/alp-tutorial.mdx:86:is that you'll see HTTP traffic flows in the web console in features like Service Graph.
./calico-enterprise_versioned_docs/version-3.17/network-policy/policy-firewalls/aws-integration/tiers-and-policy.mdx:33:We recommend restricting access to integration tiers to ensure they are not modified as they are essential to operations. When you log in to the $[prodname] web console, the following integration tiers are displayed.
./calico-enterprise_versioned_docs/version-3.17/network-policy/policy-firewalls/fortinet-integration/overview.mdx:33:**Solution**: Use FortiManager to create firewall policies that are applied as $[prodname] network policies on Kubernetes workloads. Use the power of a $[prodname] “higher-order tier” so Kubernetes policy is evaluated early in the policy processing order, but update policy using FortiManager UI. Use the $[prodname] web console as a secondary interface to verify the integration and troubleshoot using logs.
./calico-enterprise_versioned_docs/version-3.17/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:29:1. Use the $[prodname] web console to verify the integration, and then FortiManager UI to make all updates to policy rules.
./calico-enterprise_versioned_docs/version-3.17/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:47:- Login access to [the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:65:Create a [$[prodname] tier](../../policy-tiers/tiered-policy.mdx) in the $[prodname] web console for each Kubernetes cluster you want to secure. We recommend that you create a new tier (rather than reusing an existing tier) for all global network policies created by the $[prodname] integration controller.
./calico-enterprise_versioned_docs/version-3.17/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:110: | tier | Tier name you created in the web console |
./calico-enterprise_versioned_docs/version-3.17/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:154:5. Log in to the $[prodname] web console, and under the tier that you specified in the ConfigMap, verify that the GlobalNetworkPolicies are created.
./calico-enterprise_versioned_docs/version-3.17/network-policy/policy-tiers/tiered-policy.mdx:29:To create a tier and policy in the web console:
./calico-enterprise_versioned_docs/version-3.17/network-policy/policy-tiers/policy-tutorial-ui.mdx:9:- How to create a policy in the web console
./calico-enterprise_versioned_docs/version-3.17/network-policy/policy-tiers/policy-tutorial-ui.mdx:32:To follow along in the web console, click **Policies**.
./calico-enterprise_versioned_docs/version-3.17/network-policy/policy-tiers/rbac-tiered-policies.mdx:26:In $[prodname], global network policy and network policy resources are associated with a specific tier. Admins can configure access control for these $[prodname] policies using standard Kubernetes `Role` and `ClusterRole` resource types. This makes it easy to manage RBAC for both Kubernetes network policies and $[prodname] tiered network policies. RBAC permissions include managing resources using the $[prodname] web console, and `kubectl`.
./calico-enterprise_versioned_docs/version-3.17/network-policy/policy-tiers/rbac-tiered-policies.mdx:90:Create an Admin user with full access to the $[prodname] web console (as well as everything else in the cluster) using the following command. See the Kubernetes documentation to identify users based on your chosen [authentication method](https://kubernetes.io/docs/reference/access-authn-authz/authentication/), and how to use the [RBAC resources](https://kubernetes.io/docs/reference/access-authn-authz/rbac/).
./calico-enterprise_versioned_docs/version-3.17/network-policy/policy-tiers/rbac-tiered-policies.mdx:100:All users using the $[prodname] web console should be able to create authorizationreviews and authorizationrequests as well as access
./calico-enterprise_versioned_docs/version-3.17/network-policy/policy-tiers/rbac-tiered-policies.mdx:373:tier. This has the effect of making the **net-sec** tier visible in the $[prodname] web console (including listing the names of the policies it contains).
./calico-enterprise_versioned_docs/version-3.17/network-policy/policy-best-practices.mdx:333:A big obstacle to adopting Kubernetes is not having confidence that you can effectively prevent, detect, and mitigate across diverse teams. The following policy life cycle tools in the web console (**Policies** tab) can help.
./calico-enterprise_versioned_docs/version-3.17/network-policy/recommendations/learn-about-policy-recommendations.mdx:31:1. In the web console left navbar, click the **Policies** icon.
./calico-enterprise_versioned_docs/version-3.17/network-policy/recommendations/learn-about-policy-recommendations.mdx:96:1. In the web console left navbar, click **Service Graph**.
./calico-enterprise_versioned_docs/version-3.17/network-policy/recommendations/policy-recommendations.mdx:37:Basic knowledge of policies in the web console and tiers:
./calico-enterprise_versioned_docs/version-3.17/network-policy/recommendations/policy-recommendations.mdx:43:Creating and managing policy recommendations is available only in the web console.
./calico-enterprise_versioned_docs/version-3.17/network-policy/recommendations/policy-recommendations.mdx:57:1. In the left navbar in the web console, click **Policies**, **Recommendations**.
./calico-enterprise_versioned_docs/version-3.17/network-policy/beginners/calico-labels.mdx:118:$[prodname] labels must be used with the correct selector or the policy will not work as designed (and there are no error messages in the web console or when applying the YAML).
./calico-enterprise_versioned_docs/version-3.17/network-policy/beginners/simple-policy-cnx.mdx:161: Alternatively, you may also use the $[prodname] web console to inspect and view information and metrics associated with policies, endpoints, and nodes.
./calico-enterprise_versioned_docs/version-3.17/network-policy/beginners/simple-policy-cnx.mdx:218:In the $[prodname] web console, head to the dashboard view. You will see graphs associated with allowed packets/bytes and denied packets/bytes. The graphs represent the rates at which packets/bytes are being allowed or denied and are time windowed.
./calico-enterprise_versioned_docs/version-3.17/network-policy/networksets.mdx:21:If you are familiar with Service Graph in the web console, you know the value of seeing pod-to-pod traffic within your cluster. But what about traffic external to your cluster?
./calico-enterprise_versioned_docs/version-3.17/network-policy/networksets.mdx:53:In this section, we’ll walk through how to create a namespaced network set in the web console. You can follow along using your cluster or tigera-labs cluster.
./calico-enterprise_versioned_docs/version-3.17/network-policy/policy-impact-preview.mdx:23:1. From the Edit Policy page on the web console, modify any attribute of the policy.
./calico-enterprise_versioned_docs/version-3.17/visibility/alerts.mdx:18:You can manage alerts and alert events in the web console, or using the CLI. $[prodname] also provides alert templates
./calico-enterprise_versioned_docs/version-3.17/visibility/alerts.mdx:31:- [Manage alerts in the web console](#manage-alerts-in-manager-ui)
./calico-enterprise_versioned_docs/version-3.17/visibility/alerts.mdx:34:### Manage alerts in the web console
./calico-enterprise_versioned_docs/version-3.17/visibility/alerts.mdx:36:You can view alert events in the web console in several places: the **Alerts** page, **Service Graph**, and the **Kibana** dashboard.
./calico-enterprise_versioned_docs/version-3.17/visibility/alerts.mdx:117:1. In the web console, go to the **Alerts** page to view alert events.
./calico-enterprise_versioned_docs/version-3.17/visibility/packetcapture.mdx:13:$[prodname] packet capture is implemented in a Kubernetes-native way so you can troubleshoot service/application connectivity issues and performance issues. You can start a packet capture in the web console Service Graph, or using the CLI.
./calico-enterprise_versioned_docs/version-3.17/visibility/kube-audit.mdx:28:### Audit logs in the web console
./calico-enterprise_versioned_docs/version-3.17/visibility/kube-audit.mdx:30:Like $[prodname] audit logs, Kubernetes audit logs are displayed in the web console in the Timeline dashboard, Kibana dashboard (indexed by, `tigera_secure_ee_audit_kube`), and provide the core data for compliance reports.
./calico-enterprise_versioned_docs/version-3.17/visibility/kibana.mdx:24:In the web console, from the left navbar select, **Kibana**. A new browser tab opens into Kibana.
./calico-enterprise_versioned_docs/version-3.17/visibility/kibana.mdx:109:The Honeypod dashboard returns cluster-level information on workloads that have connected to Honeypod resources. These events also generate [GlobalAlerts](../reference/resources/globalalert.mdx), which populate the Alerts table in the web console.
./calico-enterprise_versioned_docs/version-3.17/visibility/elastic/audit-overview.mdx:27:### Audit logs in the web console
./calico-enterprise_versioned_docs/version-3.17/visibility/elastic/audit-overview.mdx:29:$[prodname] audit logs are displayed in the Timeline dashboard in the web console. You can filter logs, and export data in .json or .yaml formats.
./calico-enterprise_versioned_docs/version-3.17/visibility/elastic/rbac-elasticsearch.mdx:19:Elasticsearch resources are associated with the **Kubernetes API group**, `lma.tigera.io`. You can grant access to resources per cluster. The default cluster name for $[prodname] is, `cluster`. As shown in the following table, each Elasticsearch resource is mapped to a specific RBAC resource name within the `lma.tigera.io` API group. In the $[prodname] web console, Elasticsearch resources are called, **indexes or indices**.
./calico-enterprise_versioned_docs/version-3.17/visibility/elastic/rbac-elasticsearch.mdx:42:- A `tigera-network-admin` role with full permissions to create and modify resources. For help, see [Log in to the $[prodname] web console](../../operations/cnx/authentication-quickstart.mdx).
./calico-enterprise_versioned_docs/version-3.17/visibility/elastic/rbac-elasticsearch.mdx:44:- To view Elasticsearch resources in the $[prodname] web console, users must have [minimum permissions](../../network-policy/policy-tiers/rbac-tiered-policies.mdx).
./calico-enterprise_versioned_docs/version-3.17/visibility/elastic/overview.mdx:17:- View Elasticsearch logs in the $[prodname] web console (Kibana dashboard and Flow Visualizer), and the [Elasticsearch API](https://www.elastic.co/guide/en/elasticsearch/reference/current/search.html)
./calico-enterprise_versioned_docs/version-3.17/visibility/elastic/index.mdx:2:description: Configure logs for visibility in the web console.
./calico-enterprise_versioned_docs/version-3.17/visibility/elastic/troubleshoot.mdx:52:Be aware that removing LogStorage temporarily removes Elasticsearch from your cluster. Features that depend on LogStorage are temporarily unavailable, including the dashboards in the web console. Data ingestion is also temporarily paused, but will resume when the LogStorage is up and running again.
./calico-enterprise_versioned_docs/version-3.17/visibility/elastic/l7/configure.mdx:29:L7 logs are visible in the web console, service graph, in the HTTP tab.
./calico-enterprise_versioned_docs/version-3.17/visibility/elastic/l7/configure.mdx:52:- [View L7 logs in the web console](#view-l7-logs-in-manager-ui)
./calico-enterprise_versioned_docs/version-3.17/visibility/elastic/l7/configure.mdx:128:### View L7 logs in the web console
./calico-enterprise_versioned_docs/version-3.17/visibility/elastic/l7/configure.mdx:134:1. In the web console left navbar, click **Service Graph**.
./calico-enterprise_versioned_docs/version-3.17/visibility/elastic/l7/configure.mdx:143:1. In the web console left navbar, click **Kibana**.
./calico-enterprise_versioned_docs/version-3.17/visibility/get-started-cem.mdx:2:description: Tour the main features of the web console.
./calico-enterprise_versioned_docs/version-3.17/visibility/get-started-cem.mdx:12:Let's go through each item in the web console left navbar from top to bottom. You can follow along using any cluster.
./calico-enterprise_versioned_docs/version-3.17/visibility/get-started-cem.mdx:110:This page is where you switch views between clusters in the web console. When you connect to a different cluster, the entire web console view changes to reflect the selected cluster.
./calico-enterprise_versioned_docs/version-3.17/networking/egress/troubleshoot.mdx:220:In [the web console](../../visibility/get-started-cem.mdx), check for dropped packets because of policy on the outbound connection path. If you are using the iptables data plane, you can also run the following command on the client and gateway nodes to look at a lower level.
./calico-enterprise_versioned_docs/version-3.17/networking/configuring/multiple-networks.mdx:67:- [Install and configure calicoctl](../../operations/clis/calicoctl/index.mdx) or configure access to [the web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/networking/configuring/multiple-networks.mdx:198:**In the $[prodname] web console**, go to the **WorkloadEndpoint** page to see all of the WorkloadEndpoints, including the network labels are for targeting WorkloadEndpoints with policy.
./calico-enterprise_versioned_docs/version-3.17/threat/anomaly-detection/security-anomalies.mdx:26:All you need to do is install the anomaly detection within your cluster. If there are any security or performance anomalies, you will automatically get alerts in the web console.
./calico-enterprise_versioned_docs/version-3.17/threat/anomaly-detection/security-anomalies.mdx:101:- [Monitor anomaly alerts in the web console](#monitor-anomaly-alerts-in-manager-ui)
./calico-enterprise_versioned_docs/version-3.17/threat/anomaly-detection/security-anomalies.mdx:105:By default all Anomaly Detectors are disabled. To enable/disable a detector, follow these steps in the web console.
./calico-enterprise_versioned_docs/version-3.17/threat/anomaly-detection/security-anomalies.mdx:116:### Monitor anomaly alerts in the web console
./calico-enterprise_versioned_docs/version-3.17/threat/anomaly-detection/security-anomalies.mdx:120:**Monitor anomalies in the web console**
./calico-enterprise_versioned_docs/version-3.17/threat/suspicious-domains.mdx:50:#### Using the web console
./calico-enterprise_versioned_docs/version-3.17/threat/suspicious-domains.mdx:52:1. From the web console, select **Threat Feeds** --> **Add Feed**.
./calico-enterprise_versioned_docs/version-3.17/threat/suspicious-domains.mdx:130:4. In the $[prodname] web console, go the “Alerts” page to view events that are generated when an endpoint in the cluster queries a name on the list.
./calico-enterprise_versioned_docs/version-3.17/threat/web-application-firewall.mdx:34:You simply enable WAF in the web console, and determine the services that you want to enable for WAF protection. You can view WAF events as HTTP logs in Service Graph and Kibana. And you can set up global alerts to get notifications on the Alerts page.
./calico-enterprise_versioned_docs/version-3.17/threat/web-application-firewall.mdx:75:If you intend to enable WAF using the CLI rather than in the web console, or you have not yet
./calico-enterprise_versioned_docs/version-3.17/threat/web-application-firewall.mdx:102:On the web console, click **Threat Defense**, **Web Application Firewall**, **Configure Web Application Firewall**.
./calico-enterprise_versioned_docs/version-3.17/threat/web-application-firewall.mdx:136:Alternatively, you can [use the web console](#apply-waf-to-your-services) to apply WAF to the `frontend` service.
./calico-enterprise_versioned_docs/version-3.17/threat/web-application-firewall.mdx:147:1. On the web console, click **Threat Defense**, **Web Application Firewall**.
./calico-enterprise_versioned_docs/version-3.17/threat/web-application-firewall.mdx:274:Now if a SQL Injection attack is detected for rule ID 942100, you will see the global alert in the web console, Activity, Alerts.
./calico-enterprise_versioned_docs/version-3.17/threat/deeppacketinspection.mdx:13:Security teams need to run DPI quickly in response to unusual network traffic in clusters so they can identify potential threats. Also, it is critical to run DPI on select workloads (not all) to efficiently make use of cluster resources and minimize the impact of false positives. $[prodname] provides an easy way to perform DPI using [Snort community rules](https://www.snort.org/downloads/#rule-downloads). You can disable DPI at any time, selectively configure for namespaces and endpoints, and alerts are generated in the Alerts dashboard in the web console.
./calico-enterprise_versioned_docs/version-3.17/threat/deeppacketinspection.mdx:17:For each deep packet inspection resource (DeepPacketInspection), $[prodname] creates a live network monitor that inspects the header and payload information of packets that match the Snort community rules. Whenever malicious activities are suspected, an alert is automatically added to the Alerts page in the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.17/threat/deeppacketinspection.mdx:102:The alerts generated by deep packet inspection are available in the web console in the Alerts page.
./calico-enterprise_versioned_docs/version-3.17/threat/honeypod/honeypods.mdx:27:Honeypods can be configured on a per-cluster basis using "template" honeypod manifests that are easily customizable. Any alerts triggered are displayed in the Alerts tab in the $[prodname] web console. The Honeypod Dashboard in Kibana provides an easy way to monitor and analyze traffic reaching the honeypods.
./calico-enterprise_versioned_docs/version-3.17/threat/honeypod/honeypod-controller.mdx:19:Honeypods can optionally be monitored using a $[prodname] controller that periodically polls selected honeypods for suspicious activity and scans its traffic. Alerts are generated in the Events tab of the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.17/threat/tor-vpn-feed-and-dashboard.mdx:35:- Log in to the $[prodname] web console, and go to **kibana**, select **dashboard**, and select **Tor-VPN Dashboard**.
./calico-enterprise_versioned_docs/version-3.17/threat/tor-vpn-feed-and-dashboard.mdx:60:2. Now, you can monitor the Dashboard for any malicious activity. The dashboard can be found at the $[prodname] web console, go to "kibana" and then go to "Dashboard". Select "Tor-VPN Dashboard".
./calico-enterprise_versioned_docs/version-3.17/threat/suspicious-ips.mdx:53:#### Using the web console
./calico-enterprise_versioned_docs/version-3.17/threat/suspicious-ips.mdx:55:1. From the web console, select **Threat Feeds** --> **Add Feed**.
./calico-enterprise_versioned_docs/version-3.17/threat/suspicious-ips.mdx:66:> Go to the Alerts page to view events that are generated when an IP is displayed on the threat feed list. For more information, see [Manage alerts](../visibility/alerts.mdx). When you create a global threat feed in the web console, network traffic is not automatically blocked. If you find suspicious IPs on the Alerts page, you need to create a network policy to block the traffic. For help with policy, see [Block traffic to a cluster](#block-traffic-to-a-cluster).
./calico-enterprise_versioned_docs/version-3.17/threat/suspicious-ips.mdx:132:4. In the $[prodname] web console, go the “Alerts" page to view events that are generated when an IP is displayed on the threat feed list.
./calico-enterprise_versioned_docs/version-3.17/threat/suspicious-ips.mdx:223:Open the $[prodname] web console, and navigate to the “Alerts” page. If any of your pods have been communicating with the IP addresses in the FEODO tracker feed, you will see the results listed on this page. It is normal to not see any events listed on this page.
./calico-enterprise_versioned_docs/version-3.17/compliance/compliance-reports-cis.mdx:162: Upon completion, the report is available in the web console.
./calico-enterprise_versioned_docs/version-3.17/compliance/overview.mdx:193:Secure EE the web console.
./calico-enterprise_versioned_docs/version-3.17/compliance/overview.mdx:352: Upon completion, the report is available in the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.17/compliance/encrypt-cluster-pod-traffic.mdx:202:To view WireGuard statistics in the web console, you must enable them. From the left navbar, click **Dashboard**, and the Layout Settings icon.
./calico-enterprise_versioned_docs/version-3.17/compliance/encrypt-cluster-pod-traffic.mdx:208:When viewing WireGuard statistics, you might wonder why the charts in the web console Dashboard show more ingress traffic than egress if all the traffic goes within the cluster. The chart might show a 1% difference between traffic for the following reasons:
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/configure-identity-provider.mdx:12:Configure an external identity provider (IdP), create a user, and log in to the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/configure-identity-provider.mdx:39:- [Configure access to the web console](access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/configure-identity-provider.mdx:57: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/configure-identity-provider.mdx:128:1. Create values for some required variables. `MANAGER_URL` is the URL where the $[prodname] web console will be accessed,
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/configure-identity-provider.mdx:132: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/configure-identity-provider.mdx:165: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/configure-identity-provider.mdx:200: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/configure-identity-provider.mdx:256: **Problem**: Error: (502 bad gateway nginx) when logging in to the web console
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/configure-identity-provider.mdx:314:Most IdPs require redirect URIs to be allowed to redirect users at the end of the OAuth flow to the $[prodname] web console or to Kibana. Consult your IdP documentation for authorizing your domain for the respective origins and destinations.
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/configure-identity-provider.mdx:328:- If logging into Kibana fails with a `cookie not present` error, update the browser settings to allow third-party cookies, as the $[prodname] web console uses Kibana's cookies during login.
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:2:description: Configure access to the web console.
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:5:# Configure access to the web console
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:12:Configure access to the $[prodname] web console user interface.
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:16:For security, the $[prodname] web console is not exposed outside of the cluster by default. You can configure access to the $[prodname] web console using ingress, a load balancer service, or port forwarding.
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:27:| Kubernetes ingress | Configure your cluster with an ingress controller to implement the `Ingress` resource using [Kubernetes ingress](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer). | Ensure the $[prodname] web console receives a HTTPS (TLS) connection (not unencrypted HTTP). If you require TLS termination at your ingress, you must use a proxy that supports transparent HTTP/2 proxying, (for example, Envoy), or re-originate a TLS connection from your proxy to the $[prodname] web console. If you do not require TLS termination, configure your proxy to “pass thru” the TLS to the $[prodname] web console. |
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:28:| Load balancer | Configure your cluster with a service load balancer controller to implement the external load balancer. See [Kubernetes loadbalancer](https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/) | Ensure the $[prodname] web console receives a HTTPS (TLS) connection (not unencrypted HTTP). If you require TLS termination at your load balancer, you must use a load balancer that supports transparent HTTP/2 proxying, or re-originate a TLS connection from your load balancer to the $[prodname] web console. If you do not require TLS termination, configure your proxy to “pass thru” the TLS to the $[prodname] web console. |
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:29:| Port forwarding | Forward traffic from a local port to the Kubernetes API server, where it is proxied to the web console. This approach is **not recommended for production**, but is useful if you do not have a load balancer or ingress infrastructure configured, or you need to get started quickly. | n/a |
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:34:### Configure access to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:85:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:87:Access the $[prodname] web console in your browser at: `https://localhost:9443`
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:113:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:115:Access the $[prodname] web console in your browser at: `https://localhost:9443`
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:126:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:128:Access the $[prodname] web console in your browser at: `https://localhost:9443`
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:133:To expose the web console using OpenShift routes, create the following route with these required parameters:
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:161:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/access-the-manager.mdx:163:Access the $[prodname] web console in your browser using the URL with clustername. For example: `https://manager.apps.demo-ocp.tigera-solutions.io:9443`
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/index.mdx:2:description: Get started using the web console.
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/index.mdx:6:# The Calico Enterprise web console
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/authentication-quickstart.mdx:2:description: Use default token authentication to log in to the web console and Kibana.
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/authentication-quickstart.mdx:9:Get started quickly with our default token authentication to log in to the $[prodname] web console and Kibana.
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/authentication-quickstart.mdx:15:Token authentication is the default authentication option for the $[prodname] web console. When a service account is created, an
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/authentication-quickstart.mdx:17:account in to the web console and log in.
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/authentication-quickstart.mdx:23:- **the $[prodname] web console:** `https://<host>:<port>/login/token`.
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/authentication-quickstart.mdx:28:Make sure you have installed $[prodname] using one of the [installation guides](../../getting-started/index.mdx) and have set up [access to the web console](access-the-manager.mdx).
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/authentication-quickstart.mdx:38:**Log in to the $[prodname] web console**
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/authentication-quickstart.mdx:46:Give the service account permissions to access the $[prodname] web console, and a $[prodname] cluster role:
./calico-enterprise_versioned_docs/version-3.17/operations/cnx/roles-and-permissions.mdx:34:- Basic user with access to the $[prodname] web console and Kibana:
./calico-enterprise_versioned_docs/version-3.17/operations/monitor/metrics/policy-metrics.mdx:53:- the $[prodname] web console, also deployed as part of the $[prodname] manifest,
./calico-enterprise_versioned_docs/version-3.17/operations/monitor/metrics/policy-metrics.mdx:108:Using these metrics, one can identify allow, and denied byte rate and packet rate, both inbound and outbound, indexed by both policy and rule. the $[prodname] web console Dashboard makes heavy usage of these metrics.
./calico-enterprise_versioned_docs/version-3.17/operations/monitor/prometheus/byo-prometheus.mdx:32:With BYO Prometheus, $[prodname] metrics and alerts are not visible in the web console.
./calico-enterprise_versioned_docs/version-3.17/operations/monitor/prometheus/support.mdx:15: You install the $[prodname] Prometheus operator and CRDs during $[prodname] installation. $[prodname] metrics and alerts are available in the web console. You configure alerts through Prometheus AlertManager.
./calico-enterprise_versioned_docs/version-3.17/operations/index.mdx:11:## Configuring the web console
./calico-enterprise_versioned_docs/version-3.17/operations/comms/manager-tls.mdx:9:Provide TLS certificates that secure access to the $[prodname] web console user interface.
./calico-enterprise_versioned_docs/version-3.17/operations/comms/manager-tls.mdx:13:By default, the $[prodname] web console uses self-signed TLS certificates on connections. This article describes how to provide TLS certificates that users' browsers will trust.
./calico-enterprise_versioned_docs/version-3.17/operations/comms/manager-tls.mdx:17:- **Get the certificate and key pair for the $[prodname] web console**
./calico-enterprise_versioned_docs/version-3.17/operations/comms/manager-tls.mdx:18: Generate the certificate using any X.509-compatible tool or from your organization's Certificate Authority. The certificate must have Common Name or Subject Alternate Names that match the IPs or DNS names that will be used to [access the web console](../cnx/access-the-manager.mdx).
./calico-enterprise_versioned_docs/version-3.17/operations/comms/manager-tls.mdx:34:If the $[prodname] web console is already running then updating the secret should cause it to restart and pickup the new certificate and key. This will result in a short period of unavailability of the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.17/operations/comms/manager-tls.mdx:38:Additional documentation is available for securing [the $[prodname] web console connections](crypto-auth.mdx#calico-enterprise-manager-connections).
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:31:Tigera the $[prodname] web console's web interface, run from your browser, uses HTTPS to securely communicate
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:32:with the $[prodname] web console, which in turn, communicates with the Kubernetes and $[prodname] API
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:40:the $[prodname] web console through a
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:44:at the $[prodname] web console. This means that the TLS certificates used to secure traffic
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:45:between your web browser and the $[prodname] web console do not need to be shared or related
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:49:![the $[prodname] web console traffic diagram](/img/calico-enterprise/cnx-tls-mgr-comms.svg)
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:56:browser and the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:60:To properly configure TLS in the $[prodname] web console, you will need
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:69:matches the host name/DNS entry/IP address that is used to access the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:81: the certificates that the $[prodname] web console is using. This is generally caused by using
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:90: to be imported into every browser you access the $[prodname] web console from.
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:93: securely accessing the $[prodname] web console with TLS, you may want to make sure that the Common Name
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:95: entry/IP address that is used to access the $[prodname] web console (i.e. what it says in the browser
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:96: address bar). In Google Chrome you can check the $[prodname] web console certificate with Developer Tools
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:99: Subject Alternative Name and reconfigure the $[prodname] web console following the steps above.
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:104:proxies etc., between user web browsers and the $[prodname] web console. If you do so, configure your proxy
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:105:such that the $[prodname] web console receives a HTTPS (TLS) connection, not unencrypted HTTP.
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:110:- re-originate a TLS connection from your proxy to the $[prodname] web console, as it expects TLS
./calico-enterprise_versioned_docs/version-3.17/operations/comms/crypto-auth.mdx:112:If you do not require TLS termination, configure your proxy to "pass thru" the TLS to the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.17/operations/comms/apiserver-tls.mdx:32:To provide certificates for use during deployment you must create a secret before applying the 'custom-resource.yaml' or before creating the Installation resource. To specify certificates for use in the $[prodname] web console, create a secret using the following command:
./calico-enterprise_versioned_docs/version-3.17/operations/comms/apiserver-tls.mdx:52:Additional documentation is available for securing [the $[prodname] web console connections](crypto-auth.mdx#connections-from-calico-enterprise-components-to-kube-apiserver-kubernetes-and-openshift).
./calico-enterprise_versioned_docs/version-3.17/getting-started/install-on-clusters/docker-enterprise.mdx:131:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/getting-started/install-on-clusters/rancher.mdx:128:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/getting-started/install-on-clusters/windows-calico/openshift-installation.mdx:51:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/getting-started/install-on-clusters/tkg.mdx:51:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/getting-started/install-on-clusters/rancher-ui.mdx:110:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/getting-started/install-on-clusters/openshift/installation.mdx:37:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/getting-started/install-on-clusters/aks.mdx:67:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/getting-started/install-on-clusters/rke2.mdx:125:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/getting-started/install-on-clusters/eks.mdx:53:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/getting-started/install-on-clusters/gke.mdx:65:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/getting-started/install-on-clusters/kubernetes/helm.mdx:58:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/getting-started/install-on-clusters/kubernetes/quickstart.mdx:43:- [Log in to the $[prodname] web console](#log-in-to-calico-enterprise-manager)
./calico-enterprise_versioned_docs/version-3.17/getting-started/install-on-clusters/kubernetes/quickstart.mdx:158:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.17/getting-started/install-on-clusters/kubernetes/options-install.mdx:35:| **Manager** | Installs the $[prodname] web console web UI. |
./calico-enterprise_versioned_docs/version-3.17/getting-started/install-on-clusters/kubernetes/generic-install.mdx:43:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx:29:are the dashboards in the web console. Data ingestion is temporarily paused and will continue when the LogStorage is
./calico-enterprise_versioned_docs/version-3.17/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/operator.mdx:42:are the dashboards in the web console. Data ingestion is temporarily paused and will continue when the LogStorage is
./calico-enterprise_versioned_docs/version-3.17/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx:43:that depend on LogStorage are temporarily unavailable, including dashboards in the web console. Data ingestion is paused
./calico-enterprise_versioned_docs/version-3.17/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx:89:- [Configure access to the $[prodname] web console](../../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/standard.mdx:100:- [Configure access to the $[prodname] web console](../../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.17/multicluster/fine-tune-deployment.mdx:30:- Maps to port 9449 on the Manager (web console) pod
./calico-enterprise_versioned_docs/version-3.17/multicluster/fine-tune-deployment.mdx:70:- All users that log in to the $[prodname] web console must use a valid service account or user account in the management cluster.
./calico-enterprise_versioned_docs/version-3.17/multicluster/fine-tune-deployment.mdx:83:A standalone cluster uses the cluster name cluster for Elasticsearch indexes. This is also the name used by a management cluster. For a managed cluster, its cluster name is the value chosen by the user at the time of registration, through the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.17/multicluster/fine-tune-deployment.mdx:131:1. Log in to the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.17/multicluster/create-a-management-cluster.mdx:70:To access resources in a managed cluster from the $[prodname] web console within the management cluster, the logged-in user must have appropriate permissions defined in that managed cluster (clusterrole bindings).
./calico-enterprise_versioned_docs/version-3.17/reference/resources/globalalert.mdx:9:added to the Alerts page in the $[prodname] web console. Alerts may
./calico-enterprise_versioned_docs/version-3.17/reference/resources/globalalert.mdx:231:alerts in the $[prodname] web console Alert user interface. Any field
./calico-enterprise_versioned_docs/version-3.17/reference/resources/globalalert.mdx:283:These are used in the $[prodname] web console to create alerts
./calico-enterprise_versioned_docs/version-3.17/reference/resources/deeppacketinspection.mdx:11:the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.17/reference/resources/policyrecommendations.mdx:21:The policy recommendation scope is a collection of configuration options to control [policy recommendation](../../network-policy/recommendations/policy-recommendations.mdx) in the web console.
./calico-enterprise_versioned_docs/version-3.17/reference/resources/alertexception.mdx:7:An alert exception resource is a filter that hides specific alerts from users in the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.17/reference/resources/alertexception.mdx:8:You can filter alerts by time range or indefinitely. If an alert exception expires, alerts will reappear in the web console.
./calico-enterprise_versioned_docs/version-3.17/reference/resources/alertexception.mdx:40:| selector | Selects alerts to filter from the $[prodname] web console queries. | string | yes | [selector](#selector) |
./calico-enterprise_versioned_docs/version-3.17/reference/installation/_api.mdx:12527:When set to manager-tls, voltron will use the same cert bundle that the web console is served with.
./calico-enterprise_versioned_docs/version-3.17/reference/architecture/overview.mdx:129:**Main task**: Retrieves capture files (pcap format) generated by a packet capture for use with network protocol analysis tools like Wireshark. The packet capture feature is installed by default in all cluster types. Packet capture data is visible in the web console, service graph.
./calico-enterprise_versioned_docs/version-3.17/reference/anomaly-detection.mdx:11:If you have detectors currently running that are not listed on this page, they will not be managed on $[prodname] and will not show up on the web console. Delete them manually through `kubectl` by running the command: `kubectl delete globalalert tigera.io.detector.<detector-name>`, replacing `_` in the `<detector-name>` with `-`.
./calico-enterprise_versioned_docs/version-3.19-2/_includes/content/_default-install.mdx:6:| User interface | the $[prodname] web console user interface (with a default of “no access outside the cluster”). |
./calico-enterprise_versioned_docs/version-3.19-2/_includes/content/_license.mdx:9:### Does the web console display license expiration?
./calico-enterprise_versioned_docs/version-3.19-2/_includes/content/_license.mdx:11:Yes. The license indicator in the web console (top right banner) turns red when the license expires.
./calico-enterprise_versioned_docs/version-3.19-2/_includes/content/_license.mdx:19:Although users can still log in to the web console, your deployment is no longer operational. All policy enforcement stops, except for policies in the default tier. In most cases, you will experience broken connectivity (depending on your policies in the default tier). $[prodname] stops reporting flow logs, DNS logs, and $[prodname] metrics, which affects other UI elements like Service Graph and dashboards. Although some elements may appear to work, actions are not saved, and you should regard your deployment as non-functional. We recommend that you proactively manage your license to avoid disruption.
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/application-layer-policies/alp-tutorial.mdx:86:is that you'll see HTTP traffic flows in the web console in features like Service Graph.
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/policy-firewalls/fortinet-integration/overview.mdx:33:**Solution**: Use FortiManager to create firewall policies that are applied as $[prodname] network policies on Kubernetes workloads. Use the power of a $[prodname] “higher-order tier” so Kubernetes policy is evaluated early in the policy processing order, but update policy using FortiManager UI. Use the $[prodname] web console as a secondary interface to verify the integration and troubleshoot using logs.
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:29:1. Use the $[prodname] web console to verify the integration, and then FortiManager UI to make all updates to policy rules.
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:47:- Login access to [the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:65:Create a [$[prodname] tier](../../policy-tiers/tiered-policy.mdx) in the $[prodname] web console for each Kubernetes cluster you want to secure. We recommend that you create a new tier (rather than reusing an existing tier) for all global network policies created by the $[prodname] integration controller.
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:110: | tier | Tier name you created in the web console |
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:154:5. Log in to the $[prodname] web console, and under the tier that you specified in the ConfigMap, verify that the GlobalNetworkPolicies are created.
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/policy-tiers/tiered-policy.mdx:29:To create a tier and policy in the web console:
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/policy-tiers/policy-tutorial-ui.mdx:9:- How to create a policy in the web console
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/policy-tiers/policy-tutorial-ui.mdx:32:To follow along in the web console, click **Policies**.
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/policy-tiers/rbac-tiered-policies.mdx:26:In $[prodname], global network policy and network policy resources are associated with a specific tier. Admins can configure access control for these $[prodname] policies using standard Kubernetes `Role` and `ClusterRole` resource types. This makes it easy to manage RBAC for both Kubernetes network policies and $[prodname] tiered network policies. RBAC permissions include managing resources using the $[prodname] web console, and `kubectl`.
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/policy-tiers/rbac-tiered-policies.mdx:90:Create an Admin user with full access to the $[prodname] web console (as well as everything else in the cluster) using the following command. See the Kubernetes documentation to identify users based on your chosen [authentication method](https://kubernetes.io/docs/reference/access-authn-authz/authentication/), and how to use the [RBAC resources](https://kubernetes.io/docs/reference/access-authn-authz/rbac/).
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/policy-tiers/rbac-tiered-policies.mdx:100:All users using the $[prodname] web console should be able to create authorizationreviews and authorizationrequests as well as access
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/policy-tiers/rbac-tiered-policies.mdx:373:tier. This has the effect of making the **net-sec** tier visible in the $[prodname] web console (including listing the names of the policies it contains).
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/policy-best-practices.mdx:329:A big obstacle to adopting Kubernetes is not having confidence that you can effectively prevent, detect, and mitigate across diverse teams. The following policy life cycle tools in the web console (**Policies** tab) can help.
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/recommendations/learn-about-policy-recommendations.mdx:31:1. In the web console left navbar, click the **Policies** icon.
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/recommendations/learn-about-policy-recommendations.mdx:96:1. In the web console left navbar, click **Service Graph**.
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/recommendations/policy-recommendations.mdx:37:Basic knowledge of policies in the web console and tiers:
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/recommendations/policy-recommendations.mdx:43:Creating and managing policy recommendations is available only in the web console.
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/recommendations/policy-recommendations.mdx:55:### Enable policy recommendations **using the web console**
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/recommendations/policy-recommendations.mdx:57:1. In the left navbar in the web console, click **Policies**, **Recommendations**.
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/beginners/calico-labels.mdx:118:$[prodname] labels must be used with the correct selector or the policy will not work as designed (and there are no error messages in the web console or when applying the YAML).
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/beginners/simple-policy-cnx.mdx:161: Alternatively, you may also use the $[prodname] web console to inspect and view information and metrics associated with policies, endpoints, and nodes.
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/beginners/simple-policy-cnx.mdx:218:In the $[prodname] web console, head to the dashboard view. You will see graphs associated with allowed packets/bytes and denied packets/bytes. The graphs represent the rates at which packets/bytes are being allowed or denied and are time windowed.
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/networksets.mdx:21:If you are familiar with Service Graph in the web console, you know the value of seeing pod-to-pod traffic within your cluster. But what about traffic external to your cluster?
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/networksets.mdx:53:In this section, we’ll walk through how to create a namespaced network set in the web console. You can follow along using your cluster or tigera-labs cluster.
./calico-enterprise_versioned_docs/version-3.19-2/network-policy/policy-impact-preview.mdx:23:1. From the Edit Policy page on the web console, modify any attribute of the policy.
./calico-enterprise_versioned_docs/version-3.19-2/visibility/alerts.mdx:18:You can manage alerts and alert events in the web console, or using the CLI. $[prodname] also provides alert templates
./calico-enterprise_versioned_docs/version-3.19-2/visibility/alerts.mdx:31:- [Manage alerts in the web console](#manage-alerts-in-manager-ui)
./calico-enterprise_versioned_docs/version-3.19-2/visibility/alerts.mdx:34:### Manage alerts in the web console
./calico-enterprise_versioned_docs/version-3.19-2/visibility/alerts.mdx:36:You can view alert events in the web console in several places: the **Alerts** page, **Service Graph**, and the **Kibana** dashboard.
./calico-enterprise_versioned_docs/version-3.19-2/visibility/alerts.mdx:116:1. In the web console, go to the **Alerts** page to view alert events.
./calico-enterprise_versioned_docs/version-3.19-2/visibility/packetcapture.mdx:13:$[prodname] packet capture is implemented in a Kubernetes-native way so you can troubleshoot service/application connectivity issues and performance issues. You can start a packet capture in the web console Service Graph, or using the CLI.
./calico-enterprise_versioned_docs/version-3.19-2/visibility/kube-audit.mdx:28:### Audit logs in the web console
./calico-enterprise_versioned_docs/version-3.19-2/visibility/kube-audit.mdx:30:Like $[prodname] audit logs, Kubernetes audit logs are displayed in the web console in the Timeline dashboard, Kibana dashboard (indexed by, `tigera_secure_ee_audit_kube`), and provide the core data for compliance reports.
./calico-enterprise_versioned_docs/version-3.19-2/visibility/kibana.mdx:24:In the web console, from the left navbar select, **Kibana**. A new browser tab opens into Kibana.
./calico-enterprise_versioned_docs/version-3.19-2/visibility/kibana.mdx:109:The Honeypod dashboard returns cluster-level information on workloads that have connected to Honeypod resources. These events also generate [GlobalAlerts](../reference/resources/globalalert.mdx), which populate the Alerts table in the web console.
./calico-enterprise_versioned_docs/version-3.19-2/visibility/elastic/audit-overview.mdx:27:### Audit logs in the web console
./calico-enterprise_versioned_docs/version-3.19-2/visibility/elastic/audit-overview.mdx:29:$[prodname] audit logs are displayed in the Timeline dashboard in the web console. You can filter logs, and export data in .json or .yaml formats.
./calico-enterprise_versioned_docs/version-3.19-2/visibility/elastic/rbac-elasticsearch.mdx:19:Elasticsearch resources are associated with the **Kubernetes API group**, `lma.tigera.io`. You can grant access to resources per cluster. The default cluster name for $[prodname] is, `cluster`. As shown in the following table, each Elasticsearch resource is mapped to a specific RBAC resource name within the `lma.tigera.io` API group. In the $[prodname] web console, Elasticsearch resources are called, **indexes or indices**.
./calico-enterprise_versioned_docs/version-3.19-2/visibility/elastic/rbac-elasticsearch.mdx:42:- A `tigera-network-admin` role with full permissions to create and modify resources. For help, see [Log in to the $[prodname] web console](../../operations/cnx/authentication-quickstart.mdx).
./calico-enterprise_versioned_docs/version-3.19-2/visibility/elastic/rbac-elasticsearch.mdx:44:- To view Elasticsearch resources in the $[prodname] web console, users must have [minimum permissions](../../network-policy/policy-tiers/rbac-tiered-policies.mdx).
./calico-enterprise_versioned_docs/version-3.19-2/visibility/elastic/overview.mdx:17:- View Elasticsearch logs in the $[prodname] web console (Kibana dashboard and Flow Visualizer), and the [Elasticsearch API](https://www.elastic.co/guide/en/elasticsearch/reference/current/search.html)
./calico-enterprise_versioned_docs/version-3.19-2/visibility/elastic/index.mdx:2:description: Configure logs for visibility in the web console.
./calico-enterprise_versioned_docs/version-3.19-2/visibility/elastic/troubleshoot.mdx:52:Be aware that removing LogStorage temporarily removes Elasticsearch from your cluster. Features that depend on LogStorage are temporarily unavailable, including the dashboards in the web console. Data ingestion is also temporarily paused, but will resume when the LogStorage is up and running again.
./calico-enterprise_versioned_docs/version-3.19-2/visibility/elastic/l7/configure.mdx:29:L7 logs are visible in the web console, service graph, in the HTTP tab.
./calico-enterprise_versioned_docs/version-3.19-2/visibility/elastic/l7/configure.mdx:52:- [View L7 logs in the web console](#view-l7-logs-in-manager-ui)
./calico-enterprise_versioned_docs/version-3.19-2/visibility/elastic/l7/configure.mdx:120:### View L7 logs in the web console
./calico-enterprise_versioned_docs/version-3.19-2/visibility/elastic/l7/configure.mdx:126:1. In the web console left navbar, click **Service Graph**.
./calico-enterprise_versioned_docs/version-3.19-2/visibility/elastic/l7/configure.mdx:135:1. In the web console left navbar, click **Kibana**.
./calico-enterprise_versioned_docs/version-3.19-2/visibility/get-started-cem.mdx:2:description: Tour the main features of the web console.
./calico-enterprise_versioned_docs/version-3.19-2/visibility/get-started-cem.mdx:12:Let's go through each item in the web console left navbar from top to bottom. You can follow along using any cluster.
./calico-enterprise_versioned_docs/version-3.19-2/visibility/get-started-cem.mdx:110:This page is where you switch views between clusters in the web console. When you connect to a different cluster, the entire web console view changes to reflect the selected cluster.
./calico-enterprise_versioned_docs/version-3.19-2/networking/egress/troubleshoot.mdx:220:In [the web console](../../visibility/get-started-cem.mdx), check for dropped packets because of policy on the outbound connection path. If you are using the iptables data plane, you can also run the following command on the client and gateway nodes to look at a lower level.
./calico-enterprise_versioned_docs/version-3.19-2/networking/configuring/multiple-networks.mdx:67:- [Install and configure calicoctl](../../operations/clis/calicoctl/index.mdx) or configure access to [the web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/networking/configuring/multiple-networks.mdx:198:**In the $[prodname] web console**, go to the **WorkloadEndpoint** page to see all of the WorkloadEndpoints, including the network labels are for targeting WorkloadEndpoints with policy.
./calico-enterprise_versioned_docs/version-3.19-2/threat/configuring-webhooks.mdx:15:By configuring webhooks for security alerts, you can make sure that you receive critical alerts without having to sign in to the web console.
./calico-enterprise_versioned_docs/version-3.19-2/threat/configuring-webhooks.mdx:32:1. In the web console, select **Activity** > **Webhooks**, and then click **Create your first webhook**.
./calico-enterprise_versioned_docs/version-3.19-2/threat/honeypods.mdx:27:Honeypods can be configured on a per-cluster basis using "template" honeypod manifests that are easily customizable. Any alerts triggered are displayed in the Security Events tab in the $[prodname] web console. The Honeypod Dashboard in Kibana provides an easy way to monitor and analyze traffic reaching the honeypods.
./calico-enterprise_versioned_docs/version-3.19-2/threat/suspicious-domains.mdx:50:#### Using the web console
./calico-enterprise_versioned_docs/version-3.19-2/threat/suspicious-domains.mdx:52:1. From the web console, select **Threat Feeds** --> **Add Feed**.
./calico-enterprise_versioned_docs/version-3.19-2/threat/suspicious-domains.mdx:140:4. In the $[prodname] web console, go the “Security Events” page to view events that are generated when an endpoint in the cluster queries a name on the list.
./calico-enterprise_versioned_docs/version-3.19-2/threat/security-event-management.mdx:38:* In the web console, go to **Threat defense > Security Events Dashboard**.
./calico-enterprise_versioned_docs/version-3.19-2/threat/security-event-management.mdx:47:* In the web console, go to **Threat Defense > Security Events**.
./calico-enterprise_versioned_docs/version-3.19-2/threat/security-event-management.mdx:54:1. In the web console, go to **Threat Defense > Security Events**.
./calico-enterprise_versioned_docs/version-3.19-2/threat/security-event-management.mdx:64:1. In the web console, go to **Threat Defense > Security Events**.
./calico-enterprise_versioned_docs/version-3.19-2/threat/web-application-firewall.mdx:30:You simply enable WAF in the web console, and determine the services that you want to enable for WAF protection. By default WAF is set to `DetectionOnly` so no traffic will be denied until you are ready to turn on blocking mode.
./calico-enterprise_versioned_docs/version-3.19-2/threat/web-application-firewall.mdx:114:On the web console, click **Threat Defense**, **Web Application Firewall**, **Configure Web Application Firewall**.
./calico-enterprise_versioned_docs/version-3.19-2/threat/web-application-firewall.mdx:126:Alternatively, you can use the web console to apply WAF to the `frontend` service.
./calico-enterprise_versioned_docs/version-3.19-2/threat/web-application-firewall.mdx:134:1. On the web console, click **Threat Defense**, **Web Application Firewall**.
./calico-enterprise_versioned_docs/version-3.19-2/threat/deeppacketinspection.mdx:13:Security teams need to run DPI quickly in response to unusual network traffic in clusters so they can identify potential threats. Also, it is critical to run DPI on select workloads (not all) to efficiently make use of cluster resources and minimize the impact of false positives. $[prodname] provides an easy way to perform DPI using [Snort community rules](https://www.snort.org/downloads/#rule-downloads). You can disable DPI at any time, selectively configure for namespaces and endpoints, and alerts are generated in the Alerts dashboard in the web console.
./calico-enterprise_versioned_docs/version-3.19-2/threat/deeppacketinspection.mdx:17:For each deep packet inspection resource (DeepPacketInspection), $[prodname] creates a live network monitor that inspects the header and payload information of packets that match the Snort community rules. Whenever malicious activities are suspected, an alert is automatically added to the Alerts page in the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.19-2/threat/deeppacketinspection.mdx:102:The alerts generated by deep packet inspection are available in the web console in the Alerts page.
./calico-enterprise_versioned_docs/version-3.19-2/threat/tor-vpn-feed-and-dashboard.mdx:35:- Log in to the $[prodname] web console, and go to **kibana**, select **dashboard**, and select **Tor-VPN Dashboard**.
./calico-enterprise_versioned_docs/version-3.19-2/threat/tor-vpn-feed-and-dashboard.mdx:60:2. Now, you can monitor the Dashboard for any malicious activity. The dashboard can be found at the $[prodname] web console, go to "kibana" and then go to "Dashboard". Select "Tor-VPN Dashboard".
./calico-enterprise_versioned_docs/version-3.19-2/threat/suspicious-ips.mdx:53:#### Using the web console
./calico-enterprise_versioned_docs/version-3.19-2/threat/suspicious-ips.mdx:55:1. From the web console, select **Threat Feeds** --> **Add Feed**.
./calico-enterprise_versioned_docs/version-3.19-2/threat/suspicious-ips.mdx:66:> Go to the Security Events page to view events that are generated when an IP is displayed on the threat feed list. For more information, see [Manage alerts](../visibility/alerts.mdx). When you create a global threat feed in the web console, network traffic is not automatically blocked. If you find suspicious IPs on the Security Events page, you need to create a network policy to block the traffic. For help with policy, see [Block traffic to a cluster](#block-traffic-to-a-cluster).
./calico-enterprise_versioned_docs/version-3.19-2/threat/suspicious-ips.mdx:142:4. In the $[prodname] web console, go the “Security Events" page to view events that are generated when an IP is displayed on the threat feed list.
./calico-enterprise_versioned_docs/version-3.19-2/threat/suspicious-ips.mdx:233:Open the $[prodname] web console, and navigate to the “Security Events” page. If any of your pods have been communicating with the IP addresses in the FEODO tracker feed, you will see the results listed on this page. It is normal to not see any events listed on this page.
./calico-enterprise_versioned_docs/version-3.19-2/release-notes/index.mdx:21:We've updated the Endpoints page in the web console with a new flow logs panel so you can view and filter Endpoints associated with denied traffic. Flow log metadata includes the source, destination, ports, protocols, and other key forms. We've also updated the Policy Board to highlight policies with denied traffic.
./calico-enterprise_versioned_docs/version-3.19-2/compliance/compliance-reports-cis.mdx:162: Upon completion, the report is available in the web console.
./calico-enterprise_versioned_docs/version-3.19-2/compliance/overview.mdx:193:Secure EE the web console.
./calico-enterprise_versioned_docs/version-3.19-2/compliance/overview.mdx:352: Upon completion, the report is available in the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.19-2/compliance/encrypt-cluster-pod-traffic.mdx:202:To view WireGuard statistics in the web console, you must enable them. From the left navbar, click **Dashboard**, and the Layout Settings icon.
./calico-enterprise_versioned_docs/version-3.19-2/compliance/encrypt-cluster-pod-traffic.mdx:208:When viewing WireGuard statistics, you might wonder why the charts in the web console Dashboard show more ingress traffic than egress if all the traffic goes within the cluster. The chart might show a 1% difference between traffic for the following reasons:
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/configure-identity-provider.mdx:12:Configure an external identity provider (IdP), create a user, and log in to the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/configure-identity-provider.mdx:39:- [Configure access to the web console](access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/configure-identity-provider.mdx:57: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/configure-identity-provider.mdx:128:1. Create values for some required variables. `MANAGER_URL` is the URL where the $[prodname] web console will be accessed,
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/configure-identity-provider.mdx:132: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/configure-identity-provider.mdx:165: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/configure-identity-provider.mdx:200: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/configure-identity-provider.mdx:256: **Problem**: Error: (502 bad gateway nginx) when logging in to the web console
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/configure-identity-provider.mdx:314:Most IdPs require redirect URIs to be allowed to redirect users at the end of the OAuth flow to the $[prodname] web console or to Kibana. Consult your IdP documentation for authorizing your domain for the respective origins and destinations.
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/configure-identity-provider.mdx:328:- If logging into Kibana fails with a `cookie not present` error, update the browser settings to allow third-party cookies, as the $[prodname] web console uses Kibana's cookies during login.
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:2:description: Configure access to the web console.
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:5:# Configure access to the web console
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:12:Configure access to the $[prodname] web console user interface.
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:16:For security, the $[prodname] web console is not exposed outside of the cluster by default. You can configure access to the $[prodname] web console using ingress, a load balancer service, or port forwarding.
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:27:| Kubernetes ingress | Configure your cluster with an ingress controller to implement the `Ingress` resource using [Kubernetes ingress](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer). | Ensure the $[prodname] web console receives a HTTPS (TLS) connection (not unencrypted HTTP). If you require TLS termination at your ingress, you must use a proxy that supports transparent HTTP/2 proxying, (for example, Envoy), or re-originate a TLS connection from your proxy to the $[prodname] web console. If you do not require TLS termination, configure your proxy to “pass thru” the TLS to the $[prodname] web console. |
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:28:| Load balancer | Configure your cluster with a service load balancer controller to implement the external load balancer. See [Kubernetes loadbalancer](https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/) | Ensure the $[prodname] web console receives a HTTPS (TLS) connection (not unencrypted HTTP). If you require TLS termination at your load balancer, you must use a load balancer that supports transparent HTTP/2 proxying, or re-originate a TLS connection from your load balancer to the $[prodname] web console. If you do not require TLS termination, configure your proxy to “pass thru” the TLS to the $[prodname] web console. |
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:29:| Port forwarding | Forward traffic from a local port to the Kubernetes API server, where it is proxied to the web console. This approach is **not recommended for production**, but is useful if you do not have a load balancer or ingress infrastructure configured, or you need to get started quickly. | n/a |
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:34:### Configure access to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:85:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:87:Access the $[prodname] web console in your browser at: `https://localhost:9443`
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:113:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:115:Access the $[prodname] web console in your browser at: `https://localhost:9443`
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:126:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:128:Access the $[prodname] web console in your browser at: `https://localhost:9443`
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:133:To expose the web console using OpenShift routes, create the following route with these required parameters:
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:161:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/access-the-manager.mdx:163:Access the $[prodname] web console in your browser using the URL with clustername. For example: `https://manager.apps.demo-ocp.tigera-solutions.io:9443`
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/index.mdx:2:description: Get started using the web console.
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/index.mdx:6:# The Calico Enterprise web console
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/authentication-quickstart.mdx:2:description: Use default token authentication to log in to the web console and Kibana.
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/authentication-quickstart.mdx:9:Get started quickly with our default token authentication to log in to the $[prodname] web console and Kibana.
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/authentication-quickstart.mdx:15:Token authentication is the default authentication option for the $[prodname] web console. When a service account is created, an
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/authentication-quickstart.mdx:17:account in to the web console and log in.
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/authentication-quickstart.mdx:23:- **the $[prodname] web console:** `https://<host>:<port>/login/token`.
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/authentication-quickstart.mdx:28:Make sure you have installed $[prodname] using one of the [installation guides](../../getting-started/index.mdx) and have set up [access to the web console](access-the-manager.mdx).
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/authentication-quickstart.mdx:38:**Log in to the $[prodname] web console**
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/authentication-quickstart.mdx:46:Give the service account permissions to access the $[prodname] web console, and a $[prodname] cluster role:
./calico-enterprise_versioned_docs/version-3.19-2/operations/cnx/roles-and-permissions.mdx:34:- Basic user with access to the $[prodname] web console and Kibana:
./calico-enterprise_versioned_docs/version-3.19-2/operations/monitor/metrics/recommended-metrics.mdx:305:The following policy metrics are a separate endpoint exposed by Felix that are used in the web console. They require special Prometheus configuration to scrape the metrics. For details, see [Policy metrics](./policy-metrics).
./calico-enterprise_versioned_docs/version-3.19-2/operations/monitor/metrics/policy-metrics.mdx:53:- the $[prodname] web console, also deployed as part of the $[prodname] manifest,
./calico-enterprise_versioned_docs/version-3.19-2/operations/monitor/metrics/policy-metrics.mdx:108:Using these metrics, one can identify allow, and denied byte rate and packet rate, both inbound and outbound, indexed by both policy and rule. the $[prodname] web console Dashboard makes heavy usage of these metrics.
./calico-enterprise_versioned_docs/version-3.19-2/operations/monitor/prometheus/support.mdx:15:You install the $[prodname] Prometheus operator and CRDs during $[prodname] installation. $[prodname] metrics and alerts are available in the web console. You configure alerts through Prometheus AlertManager.
./calico-enterprise_versioned_docs/version-3.19-2/operations/index.mdx:11:## Configuring the web console
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/manager-tls.mdx:9:Provide TLS certificates that secure access to the $[prodname] web console user interface.
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/manager-tls.mdx:13:By default, the $[prodname] web console uses self-signed TLS certificates on connections. This article describes how to provide TLS certificates that users' browsers will trust.
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/manager-tls.mdx:17:- **Get the certificate and key pair for the $[prodname] web console**
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/manager-tls.mdx:18: Generate the certificate using any X.509-compatible tool or from your organization's Certificate Authority. The certificate must have Common Name or Subject Alternate Names that match the IPs or DNS names that will be used to [access the web console](../cnx/access-the-manager.mdx).
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/manager-tls.mdx:34:If the $[prodname] web console is already running then updating the secret should cause it to restart and pickup the new certificate and key. This will result in a short period of unavailability of the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/manager-tls.mdx:38:Additional documentation is available for securing [the $[prodname] web console connections](crypto-auth.mdx#calico-enterprise-manager-connections).
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:31:Tigera the $[prodname] web console's web interface, run from your browser, uses HTTPS to securely communicate
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:32:with the $[prodname] web console, which in turn, communicates with the Kubernetes and $[prodname] API
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:40:the $[prodname] web console through a
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:44:at the $[prodname] web console. This means that the TLS certificates used to secure traffic
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:45:between your web browser and the $[prodname] web console do not need to be shared or related
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:49:![the $[prodname] web console traffic diagram](/img/calico-enterprise/cnx-tls-mgr-comms.svg)
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:56:browser and the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:60:To properly configure TLS in the $[prodname] web console, you will need
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:69:matches the host name/DNS entry/IP address that is used to access the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:81: the certificates that the $[prodname] web console is using. This is generally caused by using
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:90: to be imported into every browser you access the $[prodname] web console from.
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:93: securely accessing the $[prodname] web console with TLS, you may want to make sure that the Common Name
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:95: entry/IP address that is used to access the $[prodname] web console (i.e. what it says in the browser
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:96: address bar). In Google Chrome you can check the $[prodname] web console certificate with Developer Tools
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:99: Subject Alternative Name and reconfigure the $[prodname] web console following the steps above.
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:104:proxies etc., between user web browsers and the $[prodname] web console. If you do so, configure your proxy
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:105:such that the $[prodname] web console receives a HTTPS (TLS) connection, not unencrypted HTTP.
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:110:- re-originate a TLS connection from your proxy to the $[prodname] web console, as it expects TLS
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/crypto-auth.mdx:112:If you do not require TLS termination, configure your proxy to "pass thru" the TLS to the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/apiserver-tls.mdx:32:To provide certificates for use during deployment you must create a secret before applying the 'custom-resource.yaml' or before creating the Installation resource. To specify certificates for use in the $[prodname] web console, create a secret using the following command:
./calico-enterprise_versioned_docs/version-3.19-2/operations/comms/apiserver-tls.mdx:52:Additional documentation is available for securing [the $[prodname] web console connections](crypto-auth.mdx#connections-from-calico-enterprise-components-to-kube-apiserver-kubernetes-and-openshift).
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/install-on-clusters/docker-enterprise.mdx:121:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/install-on-clusters/rancher.mdx:118:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/install-on-clusters/windows-calico/manual-install/openshift-installation.mdx:57:- [Configure access to the $[prodname] web console](../../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/install-on-clusters/tkg.mdx:51:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/install-on-clusters/rancher-ui.mdx:110:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/install-on-clusters/openshift/installation.mdx:37:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/install-on-clusters/aks.mdx:83:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/install-on-clusters/rke2.mdx:115:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/install-on-clusters/eks.mdx:53:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/install-on-clusters/gke.mdx:65:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/install-on-clusters/kubernetes/helm.mdx:127:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx:43:- [Log in to the $[prodname] web console](#log-in-to-calico-enterprise-manager)
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/install-on-clusters/kubernetes/quickstart.mdx:148:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/install-on-clusters/kubernetes/options-install.mdx:35:| **Manager** | Installs the $[prodname] web console web UI. |
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/install-on-clusters/kubernetes/generic-install.mdx:43:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx:29:are the dashboards in the web console. Data ingestion is temporarily paused and will continue when the LogStorage is
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/operator.mdx:42:are the dashboards in the web console. Data ingestion is temporarily paused and will continue when the LogStorage is
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx:43:that depend on LogStorage are temporarily unavailable, including dashboards in the web console. Data ingestion is paused
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx:89:- [Configure access to the $[prodname] web console](../../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/standard.mdx:100:- [Configure access to the $[prodname] web console](../../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx:148: To access resources belonging to a managed cluster from the $[prodname] web console, the service or user account used to log in must have appropriate permissions defined in the managed cluster.
./calico-enterprise_versioned_docs/version-3.19-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx:150:Define admin-level permissions for the service account `mcm-user` we created to log in to the web console. Run the following command against your managed cluster.
./calico-enterprise_versioned_docs/version-3.19-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx:162:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx:272:To access resources in a managed cluster from the $[prodname] web console within the management cluster, the logged-in user must have appropriate permissions defined in that managed cluster (clusterrole bindings).
./calico-enterprise_versioned_docs/version-3.19-2/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx:290:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.19-2/multicluster/set-up-multi-cluster-management/standard-install/create-a-management-cluster.mdx:70:To access resources in a managed cluster from the $[prodname] web console within the management cluster, the logged-in user must have appropriate permissions defined in that managed cluster (clusterrole bindings).
./calico-enterprise_versioned_docs/version-3.19-2/multicluster/fine-tune-deployment.mdx:30:- Maps to port 9449 on the Manager (web console) pod
./calico-enterprise_versioned_docs/version-3.19-2/multicluster/fine-tune-deployment.mdx:70:- All users that log in to the $[prodname] web console must use a valid service account or user account in the management cluster.
./calico-enterprise_versioned_docs/version-3.19-2/multicluster/fine-tune-deployment.mdx:83:A standalone cluster uses the cluster name cluster for Elasticsearch indexes. This is also the name used by a management cluster. For a managed cluster, its cluster name is the value chosen by the user at the time of registration, through the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.19-2/multicluster/fine-tune-deployment.mdx:131:1. Log in to the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.19-2/reference/resources/globalalert.mdx:9:added to the Alerts page in the $[prodname] web console. Alerts may
./calico-enterprise_versioned_docs/version-3.19-2/reference/resources/globalalert.mdx:224:alerts in the $[prodname] web console Alert user interface. Any field
./calico-enterprise_versioned_docs/version-3.19-2/reference/resources/globalalert.mdx:274:These are used in the $[prodname] web console to create alerts
./calico-enterprise_versioned_docs/version-3.19-2/reference/resources/deeppacketinspection.mdx:11:the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.19-2/reference/resources/policyrecommendations.mdx:21:The policy recommendation scope is a collection of configuration options to control [policy recommendation](../../network-policy/recommendations/policy-recommendations.mdx) in the web console.
./calico-enterprise_versioned_docs/version-3.19-2/reference/resources/alertexception.mdx:7:An alert exception resource is a filter that hides specific alerts from users in the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.19-2/reference/resources/alertexception.mdx:8:You can filter alerts by time range or indefinitely. If an alert exception expires, alerts will reappear in the web console.
./calico-enterprise_versioned_docs/version-3.19-2/reference/resources/alertexception.mdx:40:| selector | Selects alerts to filter from the $[prodname] web console queries. | string | yes | [selector](#selector) |
./calico-enterprise_versioned_docs/version-3.19-2/reference/installation/_api.mdx:19826:When set to manager-tls, voltron will use the same cert bundle that the web console is served with.
./calico-enterprise_versioned_docs/version-3.19-2/reference/architecture/overview.mdx:129:**Main task**: Retrieves capture files (pcap format) generated by a packet capture for use with network protocol analysis tools like Wireshark. The packet capture feature is installed by default in all cluster types. Packet capture data is visible in the web console, service graph.
./calico-enterprise_versioned_docs/version-3.20-1/_includes/content/_default-install.mdx:6:| User interface | the $[prodname] web console user interface (with a default of “no access outside the cluster”). |
./calico-enterprise_versioned_docs/version-3.20-1/_includes/content/_license.mdx:9:### Does the web console display license expiration?
./calico-enterprise_versioned_docs/version-3.20-1/_includes/content/_license.mdx:11:Yes. The license indicator in the web console (top right banner) turns red when the license expires.
./calico-enterprise_versioned_docs/version-3.20-1/_includes/content/_license.mdx:19:Although users can still log in to the web console, your deployment is no longer operational. All policy enforcement stops, except for policies in the default tier. In most cases, you will experience broken connectivity (depending on your policies in the default tier). $[prodname] stops reporting flow logs, DNS logs, and $[prodname] metrics, which affects other UI elements like Service Graph and dashboards. Although some elements may appear to work, actions are not saved, and you should regard your deployment as non-functional. We recommend that you proactively manage your license to avoid disruption.
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/application-layer-policies/alp-tutorial.mdx:86:is that you'll see HTTP traffic flows in the web console in features like Service Graph.
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/policy-firewalls/fortinet-integration/overview.mdx:33:**Solution**: Use FortiManager to create firewall policies that are applied as $[prodname] network policies on Kubernetes workloads. Use the power of a $[prodname] “higher-order tier” so Kubernetes policy is evaluated early in the policy processing order, but update policy using FortiManager UI. Use the $[prodname] web console as a secondary interface to verify the integration and troubleshoot using logs.
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:29:1. Use the $[prodname] web console to verify the integration, and then FortiManager UI to make all updates to policy rules.
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:47:- Login access to [the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:65:Create a [$[prodname] tier](../../policy-tiers/tiered-policy.mdx) in the $[prodname] web console for each Kubernetes cluster you want to secure. We recommend that you create a new tier (rather than reusing an existing tier) for all global network policies created by the $[prodname] integration controller.
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:110: | tier | Tier name you created in the web console |
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/policy-firewalls/fortinet-integration/fortimgr-integration.mdx:154:5. Log in to the $[prodname] web console, and under the tier that you specified in the ConfigMap, verify that the GlobalNetworkPolicies are created.
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/policy-tiers/tiered-policy.mdx:29:To create a tier and policy in the web console:
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/policy-tiers/policy-tutorial-ui.mdx:9:- How to create a policy in the web console
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/policy-tiers/policy-tutorial-ui.mdx:32:To follow along in the web console, click **Policies**.
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/policy-tiers/rbac-tiered-policies.mdx:26:In $[prodname], global network policy and network policy resources are associated with a specific tier. Admins can configure access control for these $[prodname] policies using standard Kubernetes `Role` and `ClusterRole` resource types. This makes it easy to manage RBAC for both Kubernetes network policies and $[prodname] tiered network policies. RBAC permissions include managing resources using the $[prodname] web console, and `kubectl`.
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/policy-tiers/rbac-tiered-policies.mdx:90:Create an Admin user with full access to the $[prodname] web console (as well as everything else in the cluster) using the following command. See the Kubernetes documentation to identify users based on your chosen [authentication method](https://kubernetes.io/docs/reference/access-authn-authz/authentication/), and how to use the [RBAC resources](https://kubernetes.io/docs/reference/access-authn-authz/rbac/).
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/policy-tiers/rbac-tiered-policies.mdx:100:All users using the $[prodname] web console should be able to create authorizationreviews and authorizationrequests as well as access
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/policy-tiers/rbac-tiered-policies.mdx:373:tier. This has the effect of making the **net-sec** tier visible in the $[prodname] web console (including listing the names of the policies it contains).
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/policy-best-practices.mdx:329:A big obstacle to adopting Kubernetes is not having confidence that you can effectively prevent, detect, and mitigate across diverse teams. The following policy life cycle tools in the web console (**Policies** tab) can help.
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/recommendations/learn-about-policy-recommendations.mdx:31:1. In the web console left navbar, click the **Policies** icon.
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/recommendations/learn-about-policy-recommendations.mdx:96:1. In the web console left navbar, click **Service Graph**.
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/recommendations/policy-recommendations.mdx:37:Basic knowledge of policies in the web console and tiers:
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/recommendations/policy-recommendations.mdx:43:Creating and managing policy recommendations is available only in the web console.
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/recommendations/policy-recommendations.mdx:57:1. In the left navbar in the web console, click **Policies**, **Recommendations**.
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/beginners/calico-labels.mdx:118:$[prodname] labels must be used with the correct selector or the policy will not work as designed (and there are no error messages in the web console or when applying the YAML).
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/beginners/simple-policy-cnx.mdx:161: Alternatively, you may also use the $[prodname] web console to inspect and view information and metrics associated with policies, endpoints, and nodes.
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/beginners/simple-policy-cnx.mdx:218:In the $[prodname] web console, head to the dashboard view. You will see graphs associated with allowed packets/bytes and denied packets/bytes. The graphs represent the rates at which packets/bytes are being allowed or denied and are time windowed.
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/networksets.mdx:21:If you are familiar with Service Graph in the web console, you know the value of seeing pod-to-pod traffic within your cluster. But what about traffic external to your cluster?
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/networksets.mdx:53:In this section, we’ll walk through how to create a namespaced network set in the web console. You can follow along using your cluster or tigera-labs cluster.
./calico-enterprise_versioned_docs/version-3.20-1/network-policy/policy-impact-preview.mdx:23:1. From the Edit Policy page on the web console, modify any attribute of the policy.
./calico-enterprise_versioned_docs/version-3.20-1/visibility/alerts.mdx:18:You can manage alerts and alert events in the web console, or using the CLI. $[prodname] also provides alert templates
./calico-enterprise_versioned_docs/version-3.20-1/visibility/alerts.mdx:31:- [Manage alerts in the web console](#manage-alerts-in-manager-ui)
./calico-enterprise_versioned_docs/version-3.20-1/visibility/alerts.mdx:34:### Manage alerts in the web console
./calico-enterprise_versioned_docs/version-3.20-1/visibility/alerts.mdx:36:You can view alert events in the web console in several places: the **Alerts** page, **Service Graph**, and the **Kibana** dashboard.
./calico-enterprise_versioned_docs/version-3.20-1/visibility/alerts.mdx:115:1. In the web console, go to the **Alerts** page to view alert events.
./calico-enterprise_versioned_docs/version-3.20-1/visibility/packetcapture.mdx:13:$[prodname] packet capture is implemented in a Kubernetes-native way so you can troubleshoot service/application connectivity issues and performance issues. You can start a packet capture in the web console Service Graph, or using the CLI.
./calico-enterprise_versioned_docs/version-3.20-1/visibility/packetcapture.mdx:72:##### Enable packet capture using the web console
./calico-enterprise_versioned_docs/version-3.20-1/visibility/packetcapture.mdx:74:1. From the web console, click the Service Graph to view the service graph diagram for your cluster.
./calico-enterprise_versioned_docs/version-3.20-1/visibility/kube-audit.mdx:28:### Audit logs in the web console
./calico-enterprise_versioned_docs/version-3.20-1/visibility/kube-audit.mdx:30:Like $[prodname] audit logs, Kubernetes audit logs are displayed in the web console in the Timeline dashboard, Kibana dashboard (indexed by, `tigera_secure_ee_audit_kube`), and provide the core data for compliance reports.
./calico-enterprise_versioned_docs/version-3.20-1/visibility/kibana.mdx:24:In the web console, from the left navbar select, **Kibana**. A new browser tab opens into Kibana.
./calico-enterprise_versioned_docs/version-3.20-1/visibility/elastic/audit-overview.mdx:27:### Audit logs in the web console
./calico-enterprise_versioned_docs/version-3.20-1/visibility/elastic/audit-overview.mdx:29:$[prodname] audit logs are displayed in the Timeline dashboard in the web console. You can filter logs, and export data in .json or .yaml formats.
./calico-enterprise_versioned_docs/version-3.20-1/visibility/elastic/rbac-elasticsearch.mdx:19:Elasticsearch resources are associated with the **Kubernetes API group**, `lma.tigera.io`. You can grant access to resources per cluster. The default cluster name for $[prodname] is, `cluster`. As shown in the following table, each Elasticsearch resource is mapped to a specific RBAC resource name within the `lma.tigera.io` API group. In the $[prodname] web console, Elasticsearch resources are called, **indexes or indices**.
./calico-enterprise_versioned_docs/version-3.20-1/visibility/elastic/rbac-elasticsearch.mdx:42:- A `tigera-network-admin` role with full permissions to create and modify resources. For help, see [Log in to the $[prodname] web console](../../operations/cnx/authentication-quickstart.mdx).
./calico-enterprise_versioned_docs/version-3.20-1/visibility/elastic/rbac-elasticsearch.mdx:44:- To view Elasticsearch resources in the $[prodname] web console, users must have [minimum permissions](../../network-policy/policy-tiers/rbac-tiered-policies.mdx).
./calico-enterprise_versioned_docs/version-3.20-1/visibility/elastic/overview.mdx:17:- View Elasticsearch logs in the $[prodname] web console (Kibana dashboard and Flow Visualizer), and the [Elasticsearch API](https://www.elastic.co/guide/en/elasticsearch/reference/current/search.html)
./calico-enterprise_versioned_docs/version-3.20-1/visibility/elastic/index.mdx:2:description: Configure logs for visibility in the web console.
./calico-enterprise_versioned_docs/version-3.20-1/visibility/elastic/troubleshoot.mdx:52:Be aware that removing LogStorage temporarily removes Elasticsearch from your cluster. Features that depend on LogStorage are temporarily unavailable, including the dashboards in the web console. Data ingestion is also temporarily paused, but will resume when the LogStorage is up and running again.
./calico-enterprise_versioned_docs/version-3.20-1/visibility/elastic/l7/configure.mdx:29:L7 logs are visible in the web console, service graph, in the HTTP tab.
./calico-enterprise_versioned_docs/version-3.20-1/visibility/elastic/l7/configure.mdx:52:- [View L7 logs in the web console](#view-l7-logs-in-manager-ui)
./calico-enterprise_versioned_docs/version-3.20-1/visibility/elastic/l7/configure.mdx:120:### View L7 logs in the web console
./calico-enterprise_versioned_docs/version-3.20-1/visibility/elastic/l7/configure.mdx:126:1. In the web console left navbar, click **Service Graph**.
./calico-enterprise_versioned_docs/version-3.20-1/visibility/elastic/l7/configure.mdx:135:1. In the web console left navbar, click **Kibana**.
./calico-enterprise_versioned_docs/version-3.20-1/visibility/get-started-cem.mdx:2:description: Tour the main features of the web console.
./calico-enterprise_versioned_docs/version-3.20-1/visibility/get-started-cem.mdx:12:Let's go through each item in the web console left navbar from top to bottom. You can follow along using any cluster.
./calico-enterprise_versioned_docs/version-3.20-1/visibility/get-started-cem.mdx:110:This page is where you switch views between clusters in the web console. When you connect to a different cluster, the entire web console view changes to reflect the selected cluster.
./calico-enterprise_versioned_docs/version-3.20-1/networking/egress/troubleshoot.mdx:220:In [the web console](../../visibility/get-started-cem.mdx), check for dropped packets because of policy on the outbound connection path. If you are using the iptables data plane, you can also run the following command on the client and gateway nodes to look at a lower level.
./calico-enterprise_versioned_docs/version-3.20-1/networking/configuring/multiple-networks.mdx:67:- [Install and configure calicoctl](../../operations/clis/calicoctl/index.mdx) or configure access to [the web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/networking/configuring/multiple-networks.mdx:198:**In the $[prodname] web console**, go to the **WorkloadEndpoint** page to see all of the WorkloadEndpoints, including the network labels are for targeting WorkloadEndpoints with policy.
./calico-enterprise_versioned_docs/version-3.20-1/threat/configuring-webhooks.mdx:25:1. In the web console, select **Activity** > **Webhooks**, and then click **Create your first webhook**.
./calico-enterprise_versioned_docs/version-3.20-1/threat/suspicious-domains.mdx:50:#### Using the web console
./calico-enterprise_versioned_docs/version-3.20-1/threat/suspicious-domains.mdx:52:1. From the web console, select **Threat Feeds** --> **Add Feed**.
./calico-enterprise_versioned_docs/version-3.20-1/threat/suspicious-domains.mdx:140:4. In the $[prodname] web console, go the “Security Events” page to view events that are generated when an endpoint in the cluster queries a name on the list.
./calico-enterprise_versioned_docs/version-3.20-1/threat/security-event-management.mdx:31:In the web console, go to **Threat defense**, **Security Events**.
./calico-enterprise_versioned_docs/version-3.20-1/threat/web-application-firewall.mdx:30:You simply enable WAF in the web console, and determine the services that you want to enable for WAF protection. By default WAF is set to `DetectionOnly` so no traffic will be denied until you are ready to turn on blocking mode.
./calico-enterprise_versioned_docs/version-3.20-1/threat/web-application-firewall.mdx:114:On the web console, click **Threat Defense**, **Web Application Firewall**, **Configure Web Application Firewall**.
./calico-enterprise_versioned_docs/version-3.20-1/threat/web-application-firewall.mdx:126:Alternatively, you can use the web console to apply WAF to the `frontend` service.
./calico-enterprise_versioned_docs/version-3.20-1/threat/web-application-firewall.mdx:134:1. On the web console, click **Threat Defense**, **Web Application Firewall**.
./calico-enterprise_versioned_docs/version-3.20-1/threat/deeppacketinspection.mdx:13:Security teams need to run DPI quickly in response to unusual network traffic in clusters so they can identify potential threats. Also, it is critical to run DPI on select workloads (not all) to efficiently make use of cluster resources and minimize the impact of false positives. $[prodname] provides an easy way to perform DPI using [Snort community rules](https://www.snort.org/downloads/#rule-downloads). You can disable DPI at any time, selectively configure for namespaces and endpoints, and alerts are generated in the Alerts dashboard in the web console.
./calico-enterprise_versioned_docs/version-3.20-1/threat/deeppacketinspection.mdx:17:For each deep packet inspection resource (DeepPacketInspection), $[prodname] creates a live network monitor that inspects the header and payload information of packets that match the Snort community rules. Whenever malicious activities are suspected, an alert is automatically added to the Alerts page in the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-1/threat/deeppacketinspection.mdx:102:The alerts generated by deep packet inspection are available in the web console in the Alerts page.
./calico-enterprise_versioned_docs/version-3.20-1/threat/tor-vpn-feed-and-dashboard.mdx:35:- Log in to the $[prodname] web console, and go to **kibana**, select **dashboard**, and select **Tor-VPN Dashboard**.
./calico-enterprise_versioned_docs/version-3.20-1/threat/tor-vpn-feed-and-dashboard.mdx:60:2. Now, you can monitor the Dashboard for any malicious activity. The dashboard can be found at the $[prodname] web console, go to "kibana" and then go to "Dashboard". Select "Tor-VPN Dashboard".
./calico-enterprise_versioned_docs/version-3.20-1/threat/suspicious-ips.mdx:53:#### Using the web console
./calico-enterprise_versioned_docs/version-3.20-1/threat/suspicious-ips.mdx:55:1. From the web console, select **Threat Feeds** --> **Add Feed**.
./calico-enterprise_versioned_docs/version-3.20-1/threat/suspicious-ips.mdx:66:> Go to the Security Events page to view events that are generated when an IP is displayed on the threat feed list. For more information, see [Manage alerts](../visibility/alerts.mdx). When you create a global threat feed in the web console, network traffic is not automatically blocked. If you find suspicious IPs on the Security Events page, you need to create a network policy to block the traffic. For help with policy, see [Block traffic to a cluster](#block-traffic-to-a-cluster).
./calico-enterprise_versioned_docs/version-3.20-1/threat/suspicious-ips.mdx:142:4. In the $[prodname] web console, go the “Security Events" page to view events that are generated when an IP is displayed on the threat feed list.
./calico-enterprise_versioned_docs/version-3.20-1/threat/suspicious-ips.mdx:233:Open the $[prodname] web console, and navigate to the “Security Events” page. If any of your pods have been communicating with the IP addresses in the FEODO tracker feed, you will see the results listed on this page. It is normal to not see any events listed on this page.
./calico-enterprise_versioned_docs/version-3.20-1/compliance/compliance-reports-cis.mdx:166: Upon completion, the report is available in the web console.
./calico-enterprise_versioned_docs/version-3.20-1/compliance/overview.mdx:195:Secure EE the web console.
./calico-enterprise_versioned_docs/version-3.20-1/compliance/overview.mdx:354: Upon completion, the report is available in the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-1/compliance/encrypt-cluster-pod-traffic.mdx:202:To view WireGuard statistics in the web console, you must enable them. From the left navbar, click **Dashboard**, and the Layout Settings icon.
./calico-enterprise_versioned_docs/version-3.20-1/compliance/encrypt-cluster-pod-traffic.mdx:208:When viewing WireGuard statistics, you might wonder why the charts in the web console Dashboard show more ingress traffic than egress if all the traffic goes within the cluster. The chart might show a 1% difference between traffic for the following reasons:
./calico-enterprise_versioned_docs/version-3.20-1/compliance/enable-compliance.mdx:38:### Enable compliance reports using the web console
./calico-enterprise_versioned_docs/version-3.20-1/compliance/enable-compliance.mdx:40:On the web console, click **Compliance Reports**, **Enable Compliance Reports**.
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/configure-identity-provider.mdx:12:Configure an external identity provider (IdP), create a user, and log in to the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/configure-identity-provider.mdx:39:- [Configure access to the web console](access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/configure-identity-provider.mdx:57: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/configure-identity-provider.mdx:128:1. Create values for some required variables. `MANAGER_URL` is the URL where the $[prodname] web console will be accessed,
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/configure-identity-provider.mdx:132: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/configure-identity-provider.mdx:165: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/configure-identity-provider.mdx:200: # This indicates where the web console can be accessed from the browser. Include the port only if the web console is not running on port 443.
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/configure-identity-provider.mdx:256: **Problem**: Error: (502 bad gateway nginx) when logging in to the web console
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/configure-identity-provider.mdx:314:Most IdPs require redirect URIs to be allowed to redirect users at the end of the OAuth flow to the $[prodname] web console or to Kibana. Consult your IdP documentation for authorizing your domain for the respective origins and destinations.
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/configure-identity-provider.mdx:328:- If logging into Kibana fails with a `cookie not present` error, update the browser settings to allow third-party cookies, as the $[prodname] web console uses Kibana's cookies during login.
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:2:description: Configure access to the web console.
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:5:# Configure access to the web console
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:12:Configure access to the $[prodname] web console user interface.
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:16:For security, the $[prodname] web console is not exposed outside of the cluster by default. You can configure access to the $[prodname] web console using ingress, a load balancer service, or port forwarding.
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:27:| Kubernetes ingress | Configure your cluster with an ingress controller to implement the `Ingress` resource using [Kubernetes ingress](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer). | Ensure the $[prodname] web console receives a HTTPS (TLS) connection (not unencrypted HTTP). If you require TLS termination at your ingress, you must use a proxy that supports transparent HTTP/2 proxying, (for example, Envoy), or re-originate a TLS connection from your proxy to the $[prodname] web console. If you do not require TLS termination, configure your proxy to “pass thru” the TLS to the $[prodname] web console. |
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:28:| Load balancer | Configure your cluster with a service load balancer controller to implement the external load balancer. See [Kubernetes loadbalancer](https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/) | Ensure the $[prodname] web console receives a HTTPS (TLS) connection (not unencrypted HTTP). If you require TLS termination at your load balancer, you must use a load balancer that supports transparent HTTP/2 proxying, or re-originate a TLS connection from your load balancer to the $[prodname] web console. If you do not require TLS termination, configure your proxy to “pass thru” the TLS to the $[prodname] web console. |
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:29:| Port forwarding | Forward traffic from a local port to the Kubernetes API server, where it is proxied to the web console. This approach is **not recommended for production**, but is useful if you do not have a load balancer or ingress infrastructure configured, or you need to get started quickly. | n/a |
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:34:### Configure access to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:85:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:87:Access the $[prodname] web console in your browser at: `https://localhost:9443`
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:113:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:115:Access the $[prodname] web console in your browser at: `https://localhost:9443`
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:126:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:128:Access the $[prodname] web console in your browser at: `https://localhost:9443`
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:133:To expose the web console using OpenShift routes, create the following route with these required parameters:
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:161:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/access-the-manager.mdx:163:Access the $[prodname] web console in your browser using the URL with clustername. For example: `https://manager.apps.demo-ocp.tigera-solutions.io:9443`
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/index.mdx:2:description: Get started using the web console.
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/index.mdx:6:# The Calico Enterprise web console
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/authentication-quickstart.mdx:2:description: Use default token authentication to log in to the web console and Kibana.
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/authentication-quickstart.mdx:9:Get started quickly with our default token authentication to log in to the $[prodname] web console and Kibana.
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/authentication-quickstart.mdx:15:Token authentication is the default authentication option for the $[prodname] web console. When a service account is created, an
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/authentication-quickstart.mdx:17:account in to the web console and log in.
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/authentication-quickstart.mdx:23:- **the $[prodname] web console:** `https://<host>:<port>/login/token`.
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/authentication-quickstart.mdx:28:Make sure you have installed $[prodname] using one of the [installation guides](../../getting-started/index.mdx) and have set up [access to the web console](access-the-manager.mdx).
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/authentication-quickstart.mdx:38:**Log in to the $[prodname] web console**
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/authentication-quickstart.mdx:46:Give the service account permissions to access the $[prodname] web console, and a $[prodname] cluster role:
./calico-enterprise_versioned_docs/version-3.20-1/operations/cnx/roles-and-permissions.mdx:34:- Basic user with access to the $[prodname] web console and Kibana:
./calico-enterprise_versioned_docs/version-3.20-1/operations/monitor/metrics/recommended-metrics.mdx:305:The following policy metrics are a separate endpoint exposed by Felix that are used in the web console. They require special Prometheus configuration to scrape the metrics. For details, see [Policy metrics](./policy-metrics).
./calico-enterprise_versioned_docs/version-3.20-1/operations/monitor/metrics/policy-metrics.mdx:53:- the $[prodname] web console, also deployed as part of the $[prodname] manifest,
./calico-enterprise_versioned_docs/version-3.20-1/operations/monitor/metrics/policy-metrics.mdx:108:Using these metrics, one can identify allow, and denied byte rate and packet rate, both inbound and outbound, indexed by both policy and rule. the $[prodname] web console Dashboard makes heavy usage of these metrics.
./calico-enterprise_versioned_docs/version-3.20-1/operations/monitor/prometheus/support.mdx:15:You install the $[prodname] Prometheus operator and CRDs during $[prodname] installation. $[prodname] metrics and alerts are available in the web console. You configure alerts through Prometheus AlertManager.
./calico-enterprise_versioned_docs/version-3.20-1/operations/index.mdx:11:## Configuring the web console
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/manager-tls.mdx:9:Provide TLS certificates that secure access to the $[prodname] web console user interface.
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/manager-tls.mdx:13:By default, the $[prodname] web console uses self-signed TLS certificates on connections. This article describes how to provide TLS certificates that users' browsers will trust.
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/manager-tls.mdx:17:- **Get the certificate and key pair for the $[prodname] web console**
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/manager-tls.mdx:18: Generate the certificate using any X.509-compatible tool or from your organization's Certificate Authority. The certificate must have Common Name or Subject Alternate Names that match the IPs or DNS names that will be used to [access the web console](../cnx/access-the-manager.mdx).
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/manager-tls.mdx:34:If the $[prodname] web console is already running then updating the secret should cause it to restart and pickup the new certificate and key. This will result in a short period of unavailability of the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/manager-tls.mdx:38:Additional documentation is available for securing [the $[prodname] web console connections](crypto-auth.mdx#calico-enterprise-manager-connections).
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:31:Tigera the $[prodname] web console's web interface, run from your browser, uses HTTPS to securely communicate
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:32:with the $[prodname] web console, which in turn, communicates with the Kubernetes and $[prodname] API
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:40:the $[prodname] web console through a
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:44:at the $[prodname] web console. This means that the TLS certificates used to secure traffic
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:45:between your web browser and the $[prodname] web console do not need to be shared or related
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:49:![the $[prodname] web console traffic diagram](/img/calico-enterprise/cnx-tls-mgr-comms.svg)
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:56:browser and the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:60:To properly configure TLS in the $[prodname] web console, you will need
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:69:matches the host name/DNS entry/IP address that is used to access the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:81: the certificates that the $[prodname] web console is using. This is generally caused by using
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:90: to be imported into every browser you access the $[prodname] web console from.
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:93: securely accessing the $[prodname] web console with TLS, you may want to make sure that the Common Name
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:95: entry/IP address that is used to access the $[prodname] web console (i.e. what it says in the browser
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:96: address bar). In Google Chrome you can check the $[prodname] web console certificate with Developer Tools
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:99: Subject Alternative Name and reconfigure the $[prodname] web console following the steps above.
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:104:proxies etc., between user web browsers and the $[prodname] web console. If you do so, configure your proxy
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:105:such that the $[prodname] web console receives a HTTPS (TLS) connection, not unencrypted HTTP.
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:110:- re-originate a TLS connection from your proxy to the $[prodname] web console, as it expects TLS
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/crypto-auth.mdx:112:If you do not require TLS termination, configure your proxy to "pass thru" the TLS to the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/apiserver-tls.mdx:32:To provide certificates for use during deployment you must create a secret before applying the 'custom-resource.yaml' or before creating the Installation resource. To specify certificates for use in the $[prodname] web console, create a secret using the following command:
./calico-enterprise_versioned_docs/version-3.20-1/operations/comms/apiserver-tls.mdx:52:Additional documentation is available for securing [the $[prodname] web console connections](crypto-auth.mdx#connections-from-calico-enterprise-components-to-kube-apiserver-kubernetes-and-openshift).
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/install-on-clusters/docker-enterprise.mdx:121:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/install-on-clusters/rancher.mdx:118:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/install-on-clusters/windows-calico/manual-install/openshift-installation.mdx:57:- [Configure access to the $[prodname] web console](../../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/install-on-clusters/tkg.mdx:51:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/install-on-clusters/rancher-ui.mdx:110:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/install-on-clusters/openshift/hostedcontrolplanes.mdx:194:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/install-on-clusters/openshift/installation.mdx:37:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/install-on-clusters/aks.mdx:83:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/install-on-clusters/rke2.mdx:115:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/install-on-clusters/eks.mdx:53:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/install-on-clusters/gke.mdx:65:- [Configure access to the $[prodname] web console](../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/install-on-clusters/kubernetes/helm.mdx:140:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/install-on-clusters/kubernetes/quickstart.mdx:43:- [Log in to the $[prodname] web console](#log-in-to-calico-enterprise-manager)
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/install-on-clusters/kubernetes/quickstart.mdx:154:### Log in to the $[prodname] web console
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/install-on-clusters/kubernetes/options-install.mdx:34:| **Manager** | Installs the $[prodname] web console web UI. |
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/install-on-clusters/kubernetes/generic-install.mdx:43:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx:29:are the dashboards in the web console. Data ingestion is temporarily paused and will continue when the LogStorage is
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/operator.mdx:42:are the dashboards in the web console. Data ingestion is temporarily paused and will continue when the LogStorage is
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx:43:that depend on LogStorage are temporarily unavailable, including dashboards in the web console. Data ingestion is paused
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx:89:- [Configure access to the $[prodname] web console](../../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/standard.mdx:100:- [Configure access to the $[prodname] web console](../../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx:148: To access resources belonging to a managed cluster from the $[prodname] web console, the service or user account used to log in must have appropriate permissions defined in the managed cluster.
./calico-enterprise_versioned_docs/version-3.20-1/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx:150:Define admin-level permissions for the service account `mcm-user` we created to log in to the web console. Run the following command against your managed cluster.
./calico-enterprise_versioned_docs/version-3.20-1/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx:162:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx:272:To access resources in a managed cluster from the $[prodname] web console within the management cluster, the logged-in user must have appropriate permissions defined in that managed cluster (clusterrole bindings).
./calico-enterprise_versioned_docs/version-3.20-1/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx:290:- [Configure access to the $[prodname] web console](../../../operations/cnx/access-the-manager.mdx)
./calico-enterprise_versioned_docs/version-3.20-1/multicluster/set-up-multi-cluster-management/standard-install/create-a-management-cluster.mdx:70:To access resources in a managed cluster from the $[prodname] web console within the management cluster, the logged-in user must have appropriate permissions defined in that managed cluster (clusterrole bindings).
./calico-enterprise_versioned_docs/version-3.20-1/multicluster/fine-tune-deployment.mdx:30:- Maps to port 9449 on the Manager (web console) pod
./calico-enterprise_versioned_docs/version-3.20-1/multicluster/fine-tune-deployment.mdx:70:- All users that log in to the $[prodname] web console must use a valid service account or user account in the management cluster.
./calico-enterprise_versioned_docs/version-3.20-1/multicluster/fine-tune-deployment.mdx:83:A standalone cluster uses the cluster name cluster for Elasticsearch indexes. This is also the name used by a management cluster. For a managed cluster, its cluster name is the value chosen by the user at the time of registration, through the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-1/multicluster/fine-tune-deployment.mdx:131:1. Log in to the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-1/reference/resources/globalalert.mdx:9:added to the Alerts page in the $[prodname] web console. Alerts may
./calico-enterprise_versioned_docs/version-3.20-1/reference/resources/globalalert.mdx:224:alerts in the $[prodname] web console Alert user interface. Any field
./calico-enterprise_versioned_docs/version-3.20-1/reference/resources/globalalert.mdx:274:These are used in the $[prodname] web console to create alerts
./calico-enterprise_versioned_docs/version-3.20-1/reference/resources/deeppacketinspection.mdx:11:the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-1/reference/resources/policyrecommendations.mdx:21:The policy recommendation scope is a collection of configuration options to control [policy recommendation](../../network-policy/recommendations/policy-recommendations.mdx) in the web console.
./calico-enterprise_versioned_docs/version-3.20-1/reference/resources/alertexception.mdx:7:An alert exception resource is a filter that hides specific alerts from users in the $[prodname] web console.
./calico-enterprise_versioned_docs/version-3.20-1/reference/resources/alertexception.mdx:8:You can filter alerts by time range or indefinitely. If an alert exception expires, alerts will reappear in the web console.
./calico-enterprise_versioned_docs/version-3.20-1/reference/resources/alertexception.mdx:40:| selector | Selects alerts to filter from the $[prodname] web console queries. | string | yes | [selector](#selector) |
./calico-enterprise_versioned_docs/version-3.20-1/reference/installation/_api.mdx:19846:When set to manager-tls, voltron will use the same cert bundle that the web console is served with.
./calico-enterprise_versioned_docs/version-3.20-1/reference/architecture/overview.mdx:129:**Main task**: Retrieves capture files (pcap format) generated by a packet capture for use with network protocol analysis tools like Wireshark. The packet capture feature is installed by default in all cluster types. Packet capture data is visible in the web console, service graph.
./use-cases/observability.mdx:207:The dashboards in the web console are suited to anyone who needs to observe cluster health more generally.
./use-cases/egress-access-controls.mdx:255:Network sets can be applied through kubectl or created in the Calico Enterprise or the web console.
./use-cases/microsegmentation.mdx:114:* *Declarative* - define security intentions in YAML files (or by creating a policy from the Calico Cloud or the web console)
./use-cases/microsegmentation.mdx:317:Policies created in the web console for Calico Enterprise or Calico can be staged or enforced through the UI.
./use-cases/microsegmentation.mdx:346:4. Confirm that policies exist in the correct order by using CLI tools or the web console's policy board.
./calico_versioned_docs/version-3.27/network-policy/get-started/calico-policy/calico-labels.mdx:104:$[prodname] labels must be used with the correct selector or the policy will not work as designed (and there are no error messages in the web console or when applying the YAML).
./calico_versioned_docs/version-3.27/getting-started/kubernetes/hardway/overview.mdx:20:This guide assumes proficiency with either AWS web console or CLI for provisioning and accessing nodes.
./calico_versioned_docs/version-3.27/reference/installation/_api.mdx:8079:When set to manager-tls, voltron will use the same cert bundle that the web console is served with.
./calico_versioned_docs/version-3.29/network-policy/policy-tiers/rbac-tiered-policies.mdx:26:In $[prodname], global network policy and network policy resources are associated with a specific tier. Admins can configure access control for these $[prodname] policies using standard Kubernetes `Role` and `ClusterRole` resource types. This makes it easy to manage RBAC for both Kubernetes network policies and $[prodname] tiered network policies. RBAC permissions include managing resources using the $[prodname] web console, and `kubectl`.
./calico_versioned_docs/version-3.29/network-policy/policy-tiers/rbac-tiered-policies.mdx:78:Create an Admin user with full access to the $[prodname] web console (as well as everything else in the cluster) using the following command. See the Kubernetes documentation to identify users based on your chosen [authentication method](https://kubernetes.io/docs/reference/access-authn-authz/authentication/), and how to use the [RBAC resources](https://kubernetes.io/docs/reference/access-authn-authz/rbac/).
./calico_versioned_docs/version-3.29/network-policy/policy-tiers/rbac-tiered-policies.mdx:339:tier. This has the effect of making the **net-sec** tier visible in the $[prodname] web console (including listing the names of the policies it contains).