apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T13:22:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-19-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-19.ec2.internal
      uid: d13b90ac-bfe2-4ca5-b432-68f23b21ac98
    resourceVersion: "24997"
    uid: 3a056959-4a81-4b4b-aa1a-03e37ea8c241
  spec:
    sourcePod: network-check-source-dbd9cf844-kcfnz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T13:29:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.28821ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:29:10Z"
    - latency: 1.966049ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:28:10Z"
    - latency: 1.094853ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:27:10Z"
    - latency: 946.153µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:26:10Z"
    - latency: 860.084µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:25:10Z"
    - latency: 1.008592ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:24:10Z"
    - latency: 1.021758ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:23:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T13:22:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-19-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-19.ec2.internal
      uid: d13b90ac-bfe2-4ca5-b432-68f23b21ac98
    resourceVersion: "29061"
    uid: 62805fc6-5348-4d92-bdcb-8919753637f5
  spec:
    sourcePod: network-check-source-dbd9cf844-kcfnz
    targetEndpoint: a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T13:28:10Z"
      message: 'load-balancer-api-external: tcp connection to a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.386178ms
      message: 'load-balancer-api-external: tcp connection to a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:34:10Z"
    - latency: 6.242004ms
      message: 'load-balancer-api-external: resolved host name a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:34:10Z"
    - latency: 4.505058ms
      message: 'load-balancer-api-external: tcp connection to a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:33:10Z"
    - latency: 6.618202ms
      message: 'load-balancer-api-external: resolved host name a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:33:10Z"
    - latency: 5.784865ms
      message: 'load-balancer-api-external: tcp connection to a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:32:10Z"
    - latency: 6.763215ms
      message: 'load-balancer-api-external: resolved host name a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:32:10Z"
    - latency: 4.805085ms
      message: 'load-balancer-api-external: tcp connection to a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:31:10Z"
    - latency: 7.230089ms
      message: 'load-balancer-api-external: resolved host name a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:31:10Z"
    - latency: 4.764108ms
      message: 'load-balancer-api-external: tcp connection to a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:30:10Z"
    - latency: 6.914232ms
      message: 'load-balancer-api-external: resolved host name a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:30:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T13:22:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-19-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-19.ec2.internal
      uid: d13b90ac-bfe2-4ca5-b432-68f23b21ac98
    resourceVersion: "29060"
    uid: 1abee6d1-efe0-43c4-bc06-9110a271a41a
  spec:
    sourcePod: network-check-source-dbd9cf844-kcfnz
    targetEndpoint: a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T13:28:10Z"
      message: 'load-balancer-api-internal: tcp connection to a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.323795ms
      message: 'load-balancer-api-internal: tcp connection to a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:34:10Z"
    - latency: 6.216952ms
      message: 'load-balancer-api-internal: resolved host name a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:34:10Z"
    - latency: 5.036352ms
      message: 'load-balancer-api-internal: tcp connection to a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:33:10Z"
    - latency: 6.650938ms
      message: 'load-balancer-api-internal: resolved host name a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:33:10Z"
    - latency: 5.807368ms
      message: 'load-balancer-api-internal: tcp connection to a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:32:10Z"
    - latency: 6.715531ms
      message: 'load-balancer-api-internal: resolved host name a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:32:10Z"
    - latency: 4.766991ms
      message: 'load-balancer-api-internal: tcp connection to a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:31:10Z"
    - latency: 7.289464ms
      message: 'load-balancer-api-internal: resolved host name a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:31:10Z"
    - latency: 4.808097ms
      message: 'load-balancer-api-internal: tcp connection to a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:30:10Z"
    - latency: 6.864129ms
      message: 'load-balancer-api-internal: resolved host name a7d2ad7820dfd42368ac465c2069a92e-82e32692af4dee2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:30:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T13:22:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-19-to-network-check-target-ip-10-0-128-237
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-19.ec2.internal
      uid: d13b90ac-bfe2-4ca5-b432-68f23b21ac98
    resourceVersion: "24995"
    uid: 70376d49-91e2-472b-917c-bbed0274674a
  spec:
    sourcePod: network-check-source-dbd9cf844-kcfnz
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T13:29:10Z"
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.360005ms
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:29:10Z"
    - latency: 4.02221ms
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:28:10Z"
    - latency: 2.376111ms
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:27:10Z"
    - latency: 2.332058ms
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:26:10Z"
    - latency: 2.028431ms
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:25:10Z"
    - latency: 2.068687ms
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:24:10Z"
    - latency: 2.563431ms
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:23:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T13:22:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-19-to-network-check-target-ip-10-0-136-19
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-19.ec2.internal
      uid: d13b90ac-bfe2-4ca5-b432-68f23b21ac98
    resourceVersion: "24994"
    uid: 99bdf3d9-2bc5-4639-8b82-712f152a5d09
  spec:
    sourcePod: network-check-source-dbd9cf844-kcfnz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T13:29:10Z"
      message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 905.853µs
      message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:29:10Z"
    - latency: 4.106135ms
      message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:28:10Z"
    - latency: 1.036499ms
      message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:27:10Z"
    - latency: 1.125819ms
      message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:26:10Z"
    - latency: 901.642µs
      message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:25:10Z"
    - latency: 772.352µs
      message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:24:10Z"
    - latency: 1.192081ms
      message: 'network-check-target-ip-10-0-136-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:23:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T13:22:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-19-to-network-check-target-ip-10-0-136-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-19.ec2.internal
      uid: d13b90ac-bfe2-4ca5-b432-68f23b21ac98
    resourceVersion: "24996"
    uid: 5e591607-7da0-459c-a499-b9b179699944
  spec:
    sourcePod: network-check-source-dbd9cf844-kcfnz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T13:29:10Z"
      message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.329069ms
      message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:29:10Z"
    - latency: 3.71972ms
      message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:28:10Z"
    - latency: 2.480799ms
      message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:27:10Z"
    - latency: 2.220392ms
      message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:26:10Z"
    - latency: 1.883002ms
      message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:25:10Z"
    - latency: 2.43681ms
      message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:24:10Z"
    - latency: 2.525063ms
      message: 'network-check-target-ip-10-0-136-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:23:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T13:22:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-19-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-19.ec2.internal
      uid: d13b90ac-bfe2-4ca5-b432-68f23b21ac98
    resourceVersion: "29059"
    uid: abe13a05-5754-495e-81a1-f733c8c28d5f
  spec:
    sourcePod: network-check-source-dbd9cf844-kcfnz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T13:28:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.55932ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:34:10Z"
    - latency: 1.661095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:34:10Z"
    - latency: 877.476µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:33:10Z"
    - latency: 1.675501ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:33:10Z"
    - latency: 932.063µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:32:10Z"
    - latency: 1.772256ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:32:10Z"
    - latency: 1.427126ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:31:10Z"
    - latency: 1.781807ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:31:10Z"
    - latency: 1.226634ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:30:10Z"
    - latency: 1.94529ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:30:10Z"
kind: List
metadata:
  resourceVersion: ""