apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T14:22:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-9-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-9.ec2.internal
      uid: b06a96cc-712b-41eb-84af-1b9a68e6ec25
    resourceVersion: "24304"
    uid: eb13ae90-96b6-4e67-a99a-4350b9a4282e
  spec:
    sourcePod: network-check-source-dbd9cf844-kb9kx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T14:29:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.046428ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:29:53Z"
    - latency: 944.691µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:28:53Z"
    - latency: 881.069µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:27:53Z"
    - latency: 1.009553ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:26:53Z"
    - latency: 1.016177ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:25:53Z"
    - latency: 1.049221ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:24:53Z"
    - latency: 1.047378ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:23:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T14:22:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-9-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-9.ec2.internal
      uid: b06a96cc-712b-41eb-84af-1b9a68e6ec25
    resourceVersion: "28703"
    uid: a4de606f-4eb7-40ab-a509-5e28f5c30cb6
  spec:
    sourcePod: network-check-source-dbd9cf844-kb9kx
    targetEndpoint: a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T14:28:53Z"
      message: 'load-balancer-api-external: tcp connection to a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.964964ms
      message: 'load-balancer-api-external: tcp connection to a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:34:53Z"
    - latency: 7.246839ms
      message: 'load-balancer-api-external: resolved host name a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T14:34:53Z"
    - latency: 4.57298ms
      message: 'load-balancer-api-external: tcp connection to a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:33:53Z"
    - latency: 6.960857ms
      message: 'load-balancer-api-external: resolved host name a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T14:33:53Z"
    - latency: 3.513314ms
      message: 'load-balancer-api-external: tcp connection to a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:32:53Z"
    - latency: 6.825999ms
      message: 'load-balancer-api-external: resolved host name a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T14:32:53Z"
    - latency: 4.521737ms
      message: 'load-balancer-api-external: tcp connection to a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:31:53Z"
    - latency: 7.371124ms
      message: 'load-balancer-api-external: resolved host name a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T14:31:53Z"
    - latency: 5.238833ms
      message: 'load-balancer-api-external: tcp connection to a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:30:53Z"
    - latency: 8.54116ms
      message: 'load-balancer-api-external: resolved host name a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T14:30:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T14:22:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-9-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-9.ec2.internal
      uid: b06a96cc-712b-41eb-84af-1b9a68e6ec25
    resourceVersion: "28704"
    uid: 97b1438b-a32b-485b-bd35-36f7da27736f
  spec:
    sourcePod: network-check-source-dbd9cf844-kb9kx
    targetEndpoint: a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T14:28:53Z"
      message: 'load-balancer-api-internal: tcp connection to a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.922339ms
      message: 'load-balancer-api-internal: tcp connection to a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:34:53Z"
    - latency: 7.324955ms
      message: 'load-balancer-api-internal: resolved host name a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T14:34:53Z"
    - latency: 4.604135ms
      message: 'load-balancer-api-internal: tcp connection to a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:33:53Z"
    - latency: 7.005496ms
      message: 'load-balancer-api-internal: resolved host name a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T14:33:53Z"
    - latency: 3.503228ms
      message: 'load-balancer-api-internal: tcp connection to a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:32:53Z"
    - latency: 6.917612ms
      message: 'load-balancer-api-internal: resolved host name a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T14:32:53Z"
    - latency: 4.001578ms
      message: 'load-balancer-api-internal: tcp connection to a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:31:53Z"
    - latency: 7.424871ms
      message: 'load-balancer-api-internal: resolved host name a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T14:31:53Z"
    - latency: 5.152836ms
      message: 'load-balancer-api-internal: tcp connection to a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:30:53Z"
    - latency: 8.659821ms
      message: 'load-balancer-api-internal: resolved host name a1dc2379e3e58443194384550794131e-2deabbd6dd671db5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T14:30:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T14:22:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-9-to-network-check-target-ip-10-0-129-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-9.ec2.internal
      uid: b06a96cc-712b-41eb-84af-1b9a68e6ec25
    resourceVersion: "24303"
    uid: 105ac104-df69-4873-88ba-dda0474f8744
  spec:
    sourcePod: network-check-source-dbd9cf844-kb9kx
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T14:29:53Z"
      message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.432124ms
      message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:29:53Z"
    - latency: 2.946428ms
      message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:28:53Z"
    - latency: 2.343075ms
      message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:27:53Z"
    - latency: 2.451313ms
      message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:26:53Z"
    - latency: 2.538231ms
      message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:25:53Z"
    - latency: 2.173579ms
      message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:24:53Z"
    - latency: 2.87269ms
      message: 'network-check-target-ip-10-0-129-86: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:23:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T14:22:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-9-to-network-check-target-ip-10-0-135-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-9.ec2.internal
      uid: b06a96cc-712b-41eb-84af-1b9a68e6ec25
    resourceVersion: "24300"
    uid: c9e6fb6a-7749-49ef-a29d-a926faea0855
  spec:
    sourcePod: network-check-source-dbd9cf844-kb9kx
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T14:29:53Z"
      message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.222µs
      message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:29:53Z"
    - latency: 913.299µs
      message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:28:53Z"
    - latency: 880.788µs
      message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:27:53Z"
    - latency: 904.349µs
      message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:26:53Z"
    - latency: 1.439593ms
      message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:25:53Z"
    - latency: 1.265571ms
      message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:24:53Z"
    - latency: 1.585926ms
      message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:23:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T14:22:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-9-to-network-check-target-ip-10-0-137-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-9.ec2.internal
      uid: b06a96cc-712b-41eb-84af-1b9a68e6ec25
    resourceVersion: "24302"
    uid: d87cf491-2b0a-4152-89e5-8b5f95d36b7c
  spec:
    sourcePod: network-check-source-dbd9cf844-kb9kx
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T14:29:53Z"
      message: 'network-check-target-ip-10-0-137-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.9492ms
      message: 'network-check-target-ip-10-0-137-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:29:53Z"
    - latency: 2.243266ms
      message: 'network-check-target-ip-10-0-137-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:28:53Z"
    - latency: 2.314028ms
      message: 'network-check-target-ip-10-0-137-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:27:53Z"
    - latency: 2.280156ms
      message: 'network-check-target-ip-10-0-137-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:26:53Z"
    - latency: 2.148636ms
      message: 'network-check-target-ip-10-0-137-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:25:53Z"
    - latency: 2.110656ms
      message: 'network-check-target-ip-10-0-137-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:24:53Z"
    - latency: 2.242775ms
      message: 'network-check-target-ip-10-0-137-224: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:23:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T14:22:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-9-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-9.ec2.internal
      uid: b06a96cc-712b-41eb-84af-1b9a68e6ec25
    resourceVersion: "28702"
    uid: ed72f8dd-adce-4823-9662-7a23884925df
  spec:
    sourcePod: network-check-source-dbd9cf844-kb9kx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T14:28:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.098844ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:34:53Z"
    - latency: 2.002001ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T14:34:53Z"
    - latency: 839.706µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:33:53Z"
    - latency: 1.698189ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T14:33:53Z"
    - latency: 843.813µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:32:53Z"
    - latency: 1.818534ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T14:32:53Z"
    - latency: 1.118527ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:31:53Z"
    - latency: 1.851305ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T14:31:53Z"
    - latency: 1.078386ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T14:30:53Z"
    - latency: 2.073859ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T14:30:53Z"
kind: List
metadata:
  resourceVersion: ""