apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T10:02:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-200-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-200.ec2.internal
      uid: 79faa49f-f69b-49b9-b2dc-644adc2041c6
    resourceVersion: "10830"
    uid: 88ca0e4d-ff1d-41a6-94c6-1e891e30f92b
  spec:
    sourcePod: network-check-source-65bdbbff45-w98tq
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T10:02:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-200-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-200.ec2.internal
      uid: 79faa49f-f69b-49b9-b2dc-644adc2041c6
    resourceVersion: "14272"
    uid: 6e2f2a81-c0ac-4e0f-b4d9-7d8dac126534
  spec:
    sourcePod: network-check-source-65bdbbff45-w98tq
    targetEndpoint: a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T10:08:41Z"
      message: 'load-balancer-api-external: tcp connection to a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.297687ms
      message: 'load-balancer-api-external: tcp connection to a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:08:41Z"
    - latency: 9.579848ms
      message: 'load-balancer-api-external: resolved host name a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:08:41Z"
    - latency: 4.68177ms
      message: 'load-balancer-api-external: tcp connection to a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:07:41Z"
    - latency: 7.417363ms
      message: 'load-balancer-api-external: resolved host name a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:07:41Z"
    - latency: 6.7028ms
      message: 'load-balancer-api-external: tcp connection to a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:06:41Z"
    - latency: 8.535773ms
      message: 'load-balancer-api-external: resolved host name a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:06:41Z"
    - latency: 4.880659ms
      message: 'load-balancer-api-external: tcp connection to a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:05:41Z"
    - latency: 7.41624ms
      message: 'load-balancer-api-external: resolved host name a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:05:41Z"
    - latency: 3.862717ms
      message: 'load-balancer-api-external: tcp connection to a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:04:41Z"
    - latency: 6.953159ms
      message: 'load-balancer-api-external: resolved host name a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:04:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T10:02:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-200-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-200.ec2.internal
      uid: 79faa49f-f69b-49b9-b2dc-644adc2041c6
    resourceVersion: "14273"
    uid: 9a8e89da-7d97-477d-8aab-319191c5cc68
  spec:
    sourcePod: network-check-source-65bdbbff45-w98tq
    targetEndpoint: a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T10:08:41Z"
      message: 'load-balancer-api-internal: tcp connection to a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.305136ms
      message: 'load-balancer-api-internal: tcp connection to a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:08:41Z"
    - latency: 9.474072ms
      message: 'load-balancer-api-internal: resolved host name a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:08:41Z"
    - latency: 5.409178ms
      message: 'load-balancer-api-internal: tcp connection to a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:07:41Z"
    - latency: 7.411678ms
      message: 'load-balancer-api-internal: resolved host name a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:07:41Z"
    - latency: 5.738369ms
      message: 'load-balancer-api-internal: tcp connection to a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:06:41Z"
    - latency: 8.478213ms
      message: 'load-balancer-api-internal: resolved host name a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:06:41Z"
    - latency: 4.194166ms
      message: 'load-balancer-api-internal: tcp connection to a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:05:41Z"
    - latency: 7.465062ms
      message: 'load-balancer-api-internal: resolved host name a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:05:41Z"
    - latency: 3.567894ms
      message: 'load-balancer-api-internal: tcp connection to a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:04:41Z"
    - latency: 6.892775ms
      message: 'load-balancer-api-internal: resolved host name a7c481c97f0fc4589bb2e3fb08eea373-24231d3925f4c286.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:04:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T10:02:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-200-to-network-check-target-ip-10-0-128-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-200.ec2.internal
      uid: 79faa49f-f69b-49b9-b2dc-644adc2041c6
    resourceVersion: "10829"
    uid: 8fbe4fd5-ab34-4496-808b-68b270ae52f7
  spec:
    sourcePod: network-check-source-65bdbbff45-w98tq
    targetEndpoint: 10.134.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T10:02:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-200-to-network-check-target-ip-10-0-134-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-200.ec2.internal
      uid: 79faa49f-f69b-49b9-b2dc-644adc2041c6
    resourceVersion: "10827"
    uid: f7384b6f-eeb0-46f6-ac93-4537e9b10706
  spec:
    sourcePod: network-check-source-65bdbbff45-w98tq
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T10:02:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-200-to-network-check-target-ip-10-0-140-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-200.ec2.internal
      uid: 79faa49f-f69b-49b9-b2dc-644adc2041c6
    resourceVersion: "10828"
    uid: 738cf12f-dc0f-4163-8a12-2d40863b9cb1
  spec:
    sourcePod: network-check-source-65bdbbff45-w98tq
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T10:02:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-200-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-200.ec2.internal
      uid: 79faa49f-f69b-49b9-b2dc-644adc2041c6
    resourceVersion: "14271"
    uid: 181ceaae-5f7b-4dc6-8421-c13b91f85d78
  spec:
    sourcePod: network-check-source-65bdbbff45-w98tq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T10:08:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.175865ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:08:41Z"
    - latency: 1.87173ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:08:41Z"
    - latency: 791.13µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:07:41Z"
    - latency: 1.895538ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:07:41Z"
    - latency: 891.296µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:06:41Z"
    - latency: 1.866876ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:06:41Z"
    - latency: 1.286178ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:05:41Z"
    - latency: 1.607523ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:05:41Z"
    - latency: 1.137073ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T10:04:41Z"
    - latency: 1.792534ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T10:04:41Z"
kind: List
metadata:
  resourceVersion: ""