apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:48:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-56-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-56.ec2.internal
      uid: 879065ef-fd09-4f32-a995-c80527b20847
    resourceVersion: "14825"
    uid: 6d733e77-230c-4f3c-8208-23a50b4c9176
  spec:
    sourcePod: network-check-source-65bdbbff45-r5mvt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:55:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.385174ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:55:17Z"
    - latency: 1.863246ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:54:17Z"
    - latency: 870.444µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:53:17Z"
    - latency: 1.126206ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:52:17Z"
    - latency: 811.725µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:51:17Z"
    - latency: 1.513969ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:50:17Z"
    - latency: 1.219664ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:49:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:48:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-56-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-56.ec2.internal
      uid: 879065ef-fd09-4f32-a995-c80527b20847
    resourceVersion: "14496"
    uid: 2a6bd7f2-de29-4816-a2a0-37792722fdc6
  spec:
    sourcePod: network-check-source-65bdbbff45-r5mvt
    targetEndpoint: a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:54:17Z"
      message: 'load-balancer-api-external: tcp connection to a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.202867ms
      message: 'load-balancer-api-external: tcp connection to a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:54:17Z"
    - latency: 13.011879ms
      message: 'load-balancer-api-external: resolved host name a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:54:17Z"
    - latency: 4.907161ms
      message: 'load-balancer-api-external: tcp connection to a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:53:17Z"
    - latency: 9.371563ms
      message: 'load-balancer-api-external: resolved host name a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:53:17Z"
    - latency: 5.559515ms
      message: 'load-balancer-api-external: tcp connection to a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:52:17Z"
    - latency: 8.161023ms
      message: 'load-balancer-api-external: resolved host name a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:52:17Z"
    - latency: 4.779816ms
      message: 'load-balancer-api-external: tcp connection to a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:51:17Z"
    - latency: 8.738858ms
      message: 'load-balancer-api-external: resolved host name a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:51:17Z"
    - latency: 6.660902ms
      message: 'load-balancer-api-external: tcp connection to a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:50:17Z"
    - latency: 8.289089ms
      message: 'load-balancer-api-external: resolved host name a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:50:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:48:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-56-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-56.ec2.internal
      uid: 879065ef-fd09-4f32-a995-c80527b20847
    resourceVersion: "14495"
    uid: 96da4c9e-0395-476e-9294-1dfdd7e0b9ee
  spec:
    sourcePod: network-check-source-65bdbbff45-r5mvt
    targetEndpoint: a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:54:17Z"
      message: 'load-balancer-api-internal: tcp connection to a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.91129ms
      message: 'load-balancer-api-internal: tcp connection to a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:54:17Z"
    - latency: 13.124996ms
      message: 'load-balancer-api-internal: resolved host name a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:54:17Z"
    - latency: 5.008507ms
      message: 'load-balancer-api-internal: tcp connection to a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:53:17Z"
    - latency: 9.452141ms
      message: 'load-balancer-api-internal: resolved host name a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:53:17Z"
    - latency: 4.680506ms
      message: 'load-balancer-api-internal: tcp connection to a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:52:17Z"
    - latency: 8.241176ms
      message: 'load-balancer-api-internal: resolved host name a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:52:17Z"
    - latency: 3.867151ms
      message: 'load-balancer-api-internal: tcp connection to a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:51:17Z"
    - latency: 8.660951ms
      message: 'load-balancer-api-internal: resolved host name a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:51:17Z"
    - latency: 6.66046ms
      message: 'load-balancer-api-internal: tcp connection to a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:50:17Z"
    - latency: 8.238884ms
      message: 'load-balancer-api-internal: resolved host name a86b5f829a2b041f1b607e7a33b69b7e-b88292d3faf18f2f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:50:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:48:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-56-to-network-check-target-ip-10-0-135-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-56.ec2.internal
      uid: 879065ef-fd09-4f32-a995-c80527b20847
    resourceVersion: "14823"
    uid: 09cd8699-4cea-43f6-a106-e79dfbf0fd2f
  spec:
    sourcePod: network-check-source-65bdbbff45-r5mvt
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:55:17Z"
      message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.732602ms
      message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:55:17Z"
    - latency: 2.071025ms
      message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:54:17Z"
    - latency: 909.352µs
      message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:53:17Z"
    - latency: 1.508901ms
      message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:52:17Z"
    - latency: 765.244µs
      message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:51:17Z"
    - latency: 1.134449ms
      message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:50:17Z"
    - latency: 2.077537ms
      message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:49:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:48:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-56-to-network-check-target-ip-10-0-139-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-56.ec2.internal
      uid: 879065ef-fd09-4f32-a995-c80527b20847
    resourceVersion: "14822"
    uid: 146d5bc6-f93c-4ffc-bfad-b02ca14abba9
  spec:
    sourcePod: network-check-source-65bdbbff45-r5mvt
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:55:17Z"
      message: 'network-check-target-ip-10-0-139-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.642511ms
      message: 'network-check-target-ip-10-0-139-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:55:17Z"
    - latency: 3.12006ms
      message: 'network-check-target-ip-10-0-139-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:54:17Z"
    - latency: 2.367718ms
      message: 'network-check-target-ip-10-0-139-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:53:17Z"
    - latency: 2.339021ms
      message: 'network-check-target-ip-10-0-139-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:52:17Z"
    - latency: 2.166542ms
      message: 'network-check-target-ip-10-0-139-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:51:17Z"
    - latency: 2.051236ms
      message: 'network-check-target-ip-10-0-139-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:50:17Z"
    - latency: 2.588904ms
      message: 'network-check-target-ip-10-0-139-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:49:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:48:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-56-to-network-check-target-ip-10-0-143-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-56.ec2.internal
      uid: 879065ef-fd09-4f32-a995-c80527b20847
    resourceVersion: "14824"
    uid: 467ed6b8-15dc-4c3e-ac8d-4d4d96b00e35
  spec:
    sourcePod: network-check-source-65bdbbff45-r5mvt
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:55:17Z"
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.99507ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:55:17Z"
    - latency: 2.586872ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:54:17Z"
    - latency: 2.375949ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:53:17Z"
    - latency: 2.185249ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:52:17Z"
    - latency: 2.916865ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:51:17Z"
    - latency: 2.947924ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:50:17Z"
    - latency: 2.485838ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:49:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T17:48:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-56-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-56.ec2.internal
      uid: 879065ef-fd09-4f32-a995-c80527b20847
    resourceVersion: "14494"
    uid: bb44e242-f7ce-4b64-9329-c090f3497e11
  spec:
    sourcePod: network-check-source-65bdbbff45-r5mvt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T17:54:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 984.047µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:54:17Z"
    - latency: 2.678548ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:54:17Z"
    - latency: 1.122717ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:53:17Z"
    - latency: 2.208889ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:53:17Z"
    - latency: 820.252µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:52:17Z"
    - latency: 2.069351ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:52:17Z"
    - latency: 1.608515ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:51:17Z"
    - latency: 1.707189ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:51:17Z"
    - latency: 890.117µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:50:17Z"
    - latency: 2.108545ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:50:17Z"
kind: List
metadata:
  resourceVersion: ""