apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T11:24:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-122-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-122.ec2.internal uid: e622f9eb-7ed2-4bd5-9d0e-b1d0a7beb702 resourceVersion: "62465" uid: 4ff36489-e647-4c2d-9f04-f9ec001bdce2 spec: sourcePod: network-check-source-7bc5b6bf85-jz6m4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-18T11:31:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.018942ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:06:12Z" - latency: 1.186861ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:05:12Z" - latency: 809.714µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:04:12Z" - latency: 961.976µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:03:12Z" - latency: 1.319729ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:02:12Z" - latency: 909.811µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:01:12Z" - latency: 1.000317ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:00:12Z" - latency: 1.104824ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T11:59:12Z" - latency: 1.275097ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T11:58:12Z" - latency: 1.226063ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-18T11:57:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T11:24:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-122-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-122.ec2.internal uid: e622f9eb-7ed2-4bd5-9d0e-b1d0a7beb702 resourceVersion: "62467" uid: a6fae28b-c469-43b7-8006-29fa0ebb74fa spec: sourcePod: network-check-source-7bc5b6bf85-jz6m4 targetEndpoint: a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-18T11:30:12Z" message: 'load-balancer-api-external: tcp connection to a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.192357ms message: 'load-balancer-api-external: tcp connection to a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:06:12Z" - latency: 8.094425ms message: 'load-balancer-api-external: resolved host name a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T12:06:12Z" - latency: 4.933362ms message: 'load-balancer-api-external: tcp connection to a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:05:12Z" - latency: 6.78137ms message: 'load-balancer-api-external: resolved host name a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T12:05:12Z" - latency: 3.976641ms message: 'load-balancer-api-external: tcp connection to a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:04:12Z" - latency: 7.252972ms message: 'load-balancer-api-external: resolved host name a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T12:04:12Z" - latency: 3.788166ms message: 'load-balancer-api-external: tcp connection to a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:03:12Z" - latency: 8.684223ms message: 'load-balancer-api-external: resolved host name a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T12:03:12Z" - latency: 4.846808ms message: 'load-balancer-api-external: tcp connection to a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:02:12Z" - latency: 7.824465ms message: 'load-balancer-api-external: resolved host name a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T12:02:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T11:24:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-122-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-122.ec2.internal uid: e622f9eb-7ed2-4bd5-9d0e-b1d0a7beb702 resourceVersion: "62466" uid: f1c61401-81ce-4907-bdcd-479eb24517c2 spec: sourcePod: network-check-source-7bc5b6bf85-jz6m4 targetEndpoint: a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-18T11:30:12Z" message: 'load-balancer-api-internal: tcp connection to a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.596932ms message: 'load-balancer-api-internal: tcp connection to a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:06:12Z" - latency: 7.908507ms message: 'load-balancer-api-internal: resolved host name a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T12:06:12Z" - latency: 4.927566ms message: 'load-balancer-api-internal: tcp connection to a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:05:12Z" - latency: 6.746244ms message: 'load-balancer-api-internal: resolved host name a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T12:05:12Z" - latency: 3.931722ms message: 'load-balancer-api-internal: tcp connection to a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:04:12Z" - latency: 7.315581ms message: 'load-balancer-api-internal: resolved host name a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T12:04:12Z" - latency: 3.151169ms message: 'load-balancer-api-internal: tcp connection to a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:03:12Z" - latency: 8.610307ms message: 'load-balancer-api-internal: resolved host name a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T12:03:12Z" - latency: 4.681504ms message: 'load-balancer-api-internal: tcp connection to a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:02:12Z" - latency: 7.695922ms message: 'load-balancer-api-internal: resolved host name a600abc7926f54d4a9f9a6c0afa01f84-85c58d7688a98d5e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-18T12:02:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T11:24:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-122-to-network-check-target-ip-10-0-130-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-122.ec2.internal uid: e622f9eb-7ed2-4bd5-9d0e-b1d0a7beb702 resourceVersion: "62462" uid: f8c6c9c9-332d-4f8b-9038-c0a23cd47fbb spec: sourcePod: network-check-source-7bc5b6bf85-jz6m4 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-18T11:31:12Z" message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.177799ms message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:06:12Z" - latency: 1.587464ms message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:05:12Z" - latency: 1.847336ms message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:04:12Z" - latency: 1.908752ms message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:03:12Z" - latency: 2.882544ms message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:02:12Z" - latency: 1.79931ms message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:01:12Z" - latency: 1.993609ms message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:00:12Z" - latency: 2.065751ms message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T11:59:12Z" - latency: 2.338903ms message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T11:58:12Z" - latency: 2.119545ms message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T11:57:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T11:24:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-122-to-network-check-target-ip-10-0-133-122 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-122.ec2.internal uid: e622f9eb-7ed2-4bd5-9d0e-b1d0a7beb702 resourceVersion: "62461" uid: b80c063e-3d84-4c84-9c94-82ecfe30c61e spec: sourcePod: network-check-source-7bc5b6bf85-jz6m4 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-18T11:31:12Z" message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.266691ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:06:12Z" - latency: 843.973µs message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:05:12Z" - latency: 854.269µs message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:04:12Z" - latency: 1.125452ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:03:12Z" - latency: 1.006308ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:02:12Z" - latency: 849.044µs message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:01:12Z" - latency: 1.070366ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:00:12Z" - latency: 990.791µs message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T11:59:12Z" - latency: 1.171325ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T11:58:12Z" - latency: 1.056155ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T11:57:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T11:24:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-122-to-network-check-target-ip-10-0-142-41 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-122.ec2.internal uid: e622f9eb-7ed2-4bd5-9d0e-b1d0a7beb702 resourceVersion: "62463" uid: 88bd8a43-5d5f-4665-a0c9-7029fea2b8f7 spec: sourcePod: network-check-source-7bc5b6bf85-jz6m4 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-18T11:31:12Z" message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.444443ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:06:12Z" - latency: 2.464121ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:05:12Z" - latency: 2.180667ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:04:12Z" - latency: 2.209693ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:03:12Z" - latency: 3.124127ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:02:12Z" - latency: 2.248537ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:01:12Z" - latency: 2.189323ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:00:12Z" - latency: 2.281744ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T11:59:12Z" - latency: 2.640254ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T11:58:12Z" - latency: 2.386925ms message: 'network-check-target-ip-10-0-142-41: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-18T11:57:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-18T11:24:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-122-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-122.ec2.internal uid: e622f9eb-7ed2-4bd5-9d0e-b1d0a7beb702 resourceVersion: "62464" uid: 368efed0-bde3-4553-bdd4-332fb64d4693 spec: sourcePod: network-check-source-7bc5b6bf85-jz6m4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-18T11:30:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.186819ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:06:12Z" - latency: 2.180793ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T12:06:12Z" - latency: 1.040826ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:05:12Z" - latency: 1.839061ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T12:05:12Z" - latency: 966.941µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:04:12Z" - latency: 1.740545ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T12:04:12Z" - latency: 901.756µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:03:12Z" - latency: 1.779653ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T12:03:12Z" - latency: 1.172411ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-18T12:02:12Z" - latency: 2.808995ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-18T12:02:12Z" kind: List metadata: resourceVersion: ""