apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:15:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: f6ee8b5c-1fdd-4ca3-aaa1-4da79e87033a resourceVersion: "33333" uid: 54854b38-4e10-4515-92c7-e252f0c7bb5f spec: sourcePod: network-check-source-7d88cb55d8-wzm7p targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T17:22:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.444934ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:57:40Z" - latency: 1.072447ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:40Z" - latency: 1.148011ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:40Z" - latency: 1.075919ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:40Z" - latency: 1.466651ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:40Z" - latency: 1.123563ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:52:40Z" - latency: 942.864µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:51:40Z" - latency: 789.35µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:50:40Z" - latency: 798.114µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:49:40Z" - latency: 1.007911ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:48:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:15:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: f6ee8b5c-1fdd-4ca3-aaa1-4da79e87033a resourceVersion: "33335" uid: 2fc6f36b-079b-45d4-8ed4-dd0688bfaa6c spec: sourcePod: network-check-source-7d88cb55d8-wzm7p targetEndpoint: a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:21:40Z" message: 'load-balancer-api-external: tcp connection to a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.972074ms message: 'load-balancer-api-external: tcp connection to a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:57:40Z" - latency: 8.757838ms message: 'load-balancer-api-external: resolved host name a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:57:40Z" - latency: 6.558781ms message: 'load-balancer-api-external: tcp connection to a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:40Z" - latency: 8.319779ms message: 'load-balancer-api-external: resolved host name a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:56:40Z" - latency: 5.52898ms message: 'load-balancer-api-external: tcp connection to a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:40Z" - latency: 8.247699ms message: 'load-balancer-api-external: resolved host name a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:55:40Z" - latency: 6.081663ms message: 'load-balancer-api-external: tcp connection to a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:40Z" - latency: 8.598813ms message: 'load-balancer-api-external: resolved host name a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:54:40Z" - latency: 14.766989ms message: 'load-balancer-api-external: tcp connection to a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:40Z" - latency: 8.885297ms message: 'load-balancer-api-external: resolved host name a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:53:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:15:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: f6ee8b5c-1fdd-4ca3-aaa1-4da79e87033a resourceVersion: "33334" uid: 7590ae98-721b-4128-8bdf-2b9282281cf0 spec: sourcePod: network-check-source-7d88cb55d8-wzm7p targetEndpoint: a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:21:40Z" message: 'load-balancer-api-internal: tcp connection to a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.849068ms message: 'load-balancer-api-internal: tcp connection to a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:57:40Z" - latency: 8.831429ms message: 'load-balancer-api-internal: resolved host name a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:57:40Z" - latency: 4.016349ms message: 'load-balancer-api-internal: tcp connection to a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:40Z" - latency: 8.416801ms message: 'load-balancer-api-internal: resolved host name a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:56:40Z" - latency: 5.511075ms message: 'load-balancer-api-internal: tcp connection to a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:40Z" - latency: 8.327458ms message: 'load-balancer-api-internal: resolved host name a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:55:40Z" - latency: 5.885094ms message: 'load-balancer-api-internal: tcp connection to a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:40Z" - latency: 8.545984ms message: 'load-balancer-api-internal: resolved host name a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:54:40Z" - latency: 17.898319ms message: 'load-balancer-api-internal: tcp connection to a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:40Z" - latency: 8.957757ms message: 'load-balancer-api-internal: resolved host name a9f18316d633d4dd6a2a3a835f2d668d-1883182873b1ea58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T17:53:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:15:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-network-check-target-ip-10-0-129-82 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: f6ee8b5c-1fdd-4ca3-aaa1-4da79e87033a resourceVersion: "33332" uid: a6dcfeaa-6bb9-4903-9a19-5d9a3cb74e1c spec: sourcePod: network-check-source-7d88cb55d8-wzm7p targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:22:40Z" message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.851052ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:57:40Z" - latency: 2.288321ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:40Z" - latency: 2.549891ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:40Z" - latency: 2.186461ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:40Z" - latency: 2.13041ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:40Z" - latency: 2.262468ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:52:40Z" - latency: 2.223437ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:51:40Z" - latency: 2.080895ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:50:40Z" - latency: 1.96041ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:49:40Z" - latency: 2.168509ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:48:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:15:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-network-check-target-ip-10-0-131-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: f6ee8b5c-1fdd-4ca3-aaa1-4da79e87033a resourceVersion: "33330" uid: 8eac57d1-3ee8-4fd5-8fd2-71912f8a2f1d spec: sourcePod: network-check-source-7d88cb55d8-wzm7p targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:22:40Z" message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.346782ms message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:57:40Z" - latency: 2.384638ms message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:40Z" - latency: 2.217636ms message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:40Z" - latency: 2.056306ms message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:40Z" - latency: 2.108835ms message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:40Z" - latency: 2.282862ms message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:52:40Z" - latency: 1.973184ms message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:51:40Z" - latency: 2.169156ms message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:50:40Z" - latency: 2.363713ms message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:49:40Z" - latency: 2.675181ms message: 'network-check-target-ip-10-0-131-184: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:48:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:15:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-network-check-target-ip-10-0-132-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: f6ee8b5c-1fdd-4ca3-aaa1-4da79e87033a resourceVersion: "33329" uid: 92786546-bc84-413e-83ef-30f739d1cf43 spec: sourcePod: network-check-source-7d88cb55d8-wzm7p targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:22:40Z" message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.598388ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:57:40Z" - latency: 1.19927ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:40Z" - latency: 1.386089ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:40Z" - latency: 950.291µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:40Z" - latency: 830.488µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:40Z" - latency: 1.164414ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:52:40Z" - latency: 787.272µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:51:40Z" - latency: 771.315µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:50:40Z" - latency: 808.53µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:49:40Z" - latency: 1.309714ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:48:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:15:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: f6ee8b5c-1fdd-4ca3-aaa1-4da79e87033a resourceVersion: "33331" uid: 701b00f7-3fa6-4c4f-b540-270c444ce766 spec: sourcePod: network-check-source-7d88cb55d8-wzm7p targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T17:21:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 936.485µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:57:40Z" - latency: 1.669002ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:57:40Z" - latency: 1.252024ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:56:40Z" - latency: 1.837194ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:56:40Z" - latency: 792.141µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:55:40Z" - latency: 1.603598ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:55:40Z" - latency: 920.371µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:54:40Z" - latency: 1.975345ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:54:40Z" - latency: 899.569µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T17:53:40Z" - latency: 2.118894ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T17:53:40Z" kind: List metadata: resourceVersion: ""