apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:18:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-190-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-190.us-west-2.compute.internal uid: 5a4659c0-a18e-4ace-a786-fcaec0219415 resourceVersion: "51292" uid: 6073eab8-316e-4066-a644-96c346601afe spec: sourcePod: network-check-source-6f78d59f99-hl8hq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T02:25:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 997.846µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:46:16Z" - latency: 1.533069ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:45:16Z" - latency: 1.118375ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:44:16Z" - latency: 900.056µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:43:16Z" - latency: 1.197087ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:42:16Z" - latency: 869.316µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:41:16Z" - latency: 1.582894ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:40:16Z" - latency: 1.332502ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:39:16Z" - latency: 961.958µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:38:16Z" - latency: 803.46µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:37:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:18:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-190-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-190.us-west-2.compute.internal uid: 5a4659c0-a18e-4ace-a786-fcaec0219415 resourceVersion: "46904" uid: e8d3b367-6b54-4821-824a-3dc6093ec763 spec: sourcePod: network-check-source-6f78d59f99-hl8hq targetEndpoint: a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T02:24:17Z" message: 'load-balancer-api-external: tcp connection to a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 59.81667ms message: 'load-balancer-api-external: tcp connection to a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:42:16Z" - latency: 6.263627ms message: 'load-balancer-api-external: resolved host name a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:42:16Z" - latency: 55.087171ms message: 'load-balancer-api-external: tcp connection to a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:41:16Z" - latency: 6.902987ms message: 'load-balancer-api-external: resolved host name a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:41:16Z" - latency: 51.125743ms message: 'load-balancer-api-external: tcp connection to a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:40:16Z" - latency: 6.523687ms message: 'load-balancer-api-external: resolved host name a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:40:16Z" - latency: 55.620365ms message: 'load-balancer-api-external: tcp connection to a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:39:16Z" - latency: 7.238608ms message: 'load-balancer-api-external: resolved host name a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:39:16Z" - latency: 53.736603ms message: 'load-balancer-api-external: tcp connection to a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:38:16Z" - latency: 7.402549ms message: 'load-balancer-api-external: resolved host name a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:38:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:18:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-190-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-190.us-west-2.compute.internal uid: 5a4659c0-a18e-4ace-a786-fcaec0219415 resourceVersion: "46903" uid: b193bac6-83eb-40b7-98a7-699e118584d6 spec: sourcePod: network-check-source-6f78d59f99-hl8hq targetEndpoint: a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T02:24:17Z" message: 'load-balancer-api-internal: tcp connection to a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.133975ms message: 'load-balancer-api-internal: tcp connection to a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:42:16Z" - latency: 6.192061ms message: 'load-balancer-api-internal: resolved host name a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:42:16Z" - latency: 51.81489ms message: 'load-balancer-api-internal: tcp connection to a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:41:16Z" - latency: 6.802762ms message: 'load-balancer-api-internal: resolved host name a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:41:16Z" - latency: 55.964011ms message: 'load-balancer-api-internal: tcp connection to a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:40:16Z" - latency: 6.658782ms message: 'load-balancer-api-internal: resolved host name a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:40:16Z" - latency: 55.612084ms message: 'load-balancer-api-internal: tcp connection to a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:39:16Z" - latency: 7.058652ms message: 'load-balancer-api-internal: resolved host name a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:39:16Z" - latency: 56.423479ms message: 'load-balancer-api-internal: tcp connection to a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:38:16Z" - latency: 7.34435ms message: 'load-balancer-api-internal: resolved host name a002968538e68413697f26034184b0ae-7fcf7513c18704a7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T02:38:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:18:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-190-to-network-check-target-ip-10-0-130-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-190.us-west-2.compute.internal uid: 5a4659c0-a18e-4ace-a786-fcaec0219415 resourceVersion: "51290" uid: 1488c50f-7d1d-4c2c-b588-0a7d17be158a spec: sourcePod: network-check-source-6f78d59f99-hl8hq targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T02:25:16Z" message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.463253ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:46:16Z" - latency: 2.290265ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:45:16Z" - latency: 2.365509ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:44:16Z" - latency: 2.139451ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:43:16Z" - latency: 2.299079ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:42:16Z" - latency: 2.261477ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:41:16Z" - latency: 3.171688ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:40:16Z" - latency: 2.353947ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:39:16Z" - latency: 2.437887ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:38:16Z" - latency: 2.588533ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:37:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:18:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-190-to-network-check-target-ip-10-0-131-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-190.us-west-2.compute.internal uid: 5a4659c0-a18e-4ace-a786-fcaec0219415 resourceVersion: "51288" uid: da4ea967-be35-43ac-b760-5a41624eaed8 spec: sourcePod: network-check-source-6f78d59f99-hl8hq targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T02:25:16Z" message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.130877ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:46:16Z" - latency: 2.237785ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:45:16Z" - latency: 2.608575ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:44:16Z" - latency: 2.434456ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:43:16Z" - latency: 2.359779ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:42:16Z" - latency: 2.710034ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:41:16Z" - latency: 2.340946ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:40:16Z" - latency: 2.853607ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:39:16Z" - latency: 2.3426ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:38:16Z" - latency: 2.616669ms message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:37:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:18:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-190-to-network-check-target-ip-10-0-136-190 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-190.us-west-2.compute.internal uid: 5a4659c0-a18e-4ace-a786-fcaec0219415 resourceVersion: "51287" uid: 3939703d-f4d0-4228-b04f-bd328b100b1d spec: sourcePod: network-check-source-6f78d59f99-hl8hq targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-04T02:25:16Z" message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 767.967µs message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:46:16Z" - latency: 958.58µs message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:45:16Z" - latency: 820.489µs message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:44:16Z" - latency: 1.474748ms message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:43:16Z" - latency: 909.6µs message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:42:16Z" - latency: 1.313655ms message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:41:16Z" - latency: 1.712137ms message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:40:16Z" - latency: 1.011095ms message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:39:16Z" - latency: 1.610488ms message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:38:16Z" - latency: 2.097013ms message: 'network-check-target-ip-10-0-136-190: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:37:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:18:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-190-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-190.us-west-2.compute.internal uid: 5a4659c0-a18e-4ace-a786-fcaec0219415 resourceVersion: "46900" uid: 9e473091-c663-448b-886c-74fcce3ea1a1 spec: sourcePod: network-check-source-6f78d59f99-hl8hq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T02:24:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 986.579µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:42:16Z" - latency: 1.859715ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T02:42:16Z" - latency: 880.817µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:41:16Z" - latency: 1.906342ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T02:41:16Z" - latency: 1.337838ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:40:16Z" - latency: 2.061184ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T02:40:16Z" - latency: 843.847µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:39:16Z" - latency: 1.948122ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T02:39:16Z" - latency: 946.246µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T02:38:16Z" - latency: 1.662458ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T02:38:16Z" kind: List metadata: resourceVersion: ""