apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T12:27:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-159-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-159.ec2.internal
      uid: c92ea27f-bdd4-43f9-8116-d388094911ca
    resourceVersion: "11171"
    uid: 59389932-025f-441f-af40-0d093378ad72
  spec:
    sourcePod: network-check-source-7d88cb55d8-dlkgb
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T12:27:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-159-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-159.ec2.internal
      uid: c92ea27f-bdd4-43f9-8116-d388094911ca
    resourceVersion: "14795"
    uid: f2feb306-5bcc-4ad3-9d5e-ee4b8581a683
  spec:
    sourcePod: network-check-source-7d88cb55d8-dlkgb
    targetEndpoint: a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T12:33:02Z"
      message: 'load-balancer-api-external: tcp connection to a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.452506ms
      message: 'load-balancer-api-external: tcp connection to a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T12:33:02Z"
    - latency: 9.334123ms
      message: 'load-balancer-api-external: resolved host name a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T12:33:02Z"
    - latency: 4.603236ms
      message: 'load-balancer-api-external: tcp connection to a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T12:32:02Z"
    - latency: 9.206905ms
      message: 'load-balancer-api-external: resolved host name a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T12:32:02Z"
    - latency: 5.575815ms
      message: 'load-balancer-api-external: tcp connection to a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T12:31:02Z"
    - latency: 8.781338ms
      message: 'load-balancer-api-external: resolved host name a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T12:31:02Z"
    - latency: 5.537741ms
      message: 'load-balancer-api-external: tcp connection to a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T12:30:02Z"
    - latency: 8.938764ms
      message: 'load-balancer-api-external: resolved host name a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T12:30:02Z"
    - latency: 4.086824ms
      message: 'load-balancer-api-external: tcp connection to a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T12:29:02Z"
    - latency: 8.045153ms
      message: 'load-balancer-api-external: resolved host name a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T12:29:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T12:27:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-159-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-159.ec2.internal
      uid: c92ea27f-bdd4-43f9-8116-d388094911ca
    resourceVersion: "14794"
    uid: 66ef5f9b-e26a-4af5-9c7a-21754986405f
  spec:
    sourcePod: network-check-source-7d88cb55d8-dlkgb
    targetEndpoint: a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T12:33:02Z"
      message: 'load-balancer-api-internal: tcp connection to a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.500597ms
      message: 'load-balancer-api-internal: tcp connection to a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T12:33:02Z"
    - latency: 9.23357ms
      message: 'load-balancer-api-internal: resolved host name a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T12:33:02Z"
    - latency: 4.525343ms
      message: 'load-balancer-api-internal: tcp connection to a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T12:32:02Z"
    - latency: 9.025325ms
      message: 'load-balancer-api-internal: resolved host name a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T12:32:02Z"
    - latency: 5.414992ms
      message: 'load-balancer-api-internal: tcp connection to a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T12:31:02Z"
    - latency: 8.809362ms
      message: 'load-balancer-api-internal: resolved host name a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T12:31:02Z"
    - latency: 5.529492ms
      message: 'load-balancer-api-internal: tcp connection to a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T12:30:02Z"
    - latency: 8.9108ms
      message: 'load-balancer-api-internal: resolved host name a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T12:30:02Z"
    - latency: 3.726584ms
      message: 'load-balancer-api-internal: tcp connection to a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T12:29:02Z"
    - latency: 7.943189ms
      message: 'load-balancer-api-internal: resolved host name a5884f98396e64a6996df54a71db8def-e85e726d7ac9c4ec.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T12:29:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T12:27:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-159-to-network-check-target-ip-10-0-131-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-159.ec2.internal
      uid: c92ea27f-bdd4-43f9-8116-d388094911ca
    resourceVersion: "11167"
    uid: 8cadd998-7fee-4dbc-9548-dadd29b7b204
  spec:
    sourcePod: network-check-source-7d88cb55d8-dlkgb
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T12:27:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-159-to-network-check-target-ip-10-0-136-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-159.ec2.internal
      uid: c92ea27f-bdd4-43f9-8116-d388094911ca
    resourceVersion: "11168"
    uid: 2c7cef2b-99b3-496b-b3a4-5fcece5de0b7
  spec:
    sourcePod: network-check-source-7d88cb55d8-dlkgb
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T12:27:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-159-to-network-check-target-ip-10-0-141-3
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-159.ec2.internal
      uid: c92ea27f-bdd4-43f9-8116-d388094911ca
    resourceVersion: "11169"
    uid: 537fd45b-010a-4d8b-89e7-a60fff78c300
  spec:
    sourcePod: network-check-source-7d88cb55d8-dlkgb
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T12:27:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-159-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-159.ec2.internal
      uid: c92ea27f-bdd4-43f9-8116-d388094911ca
    resourceVersion: "14793"
    uid: a3463701-6eca-4e34-8ff0-bb3996074924
  spec:
    sourcePod: network-check-source-7d88cb55d8-dlkgb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T12:33:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 912.737µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T12:33:02Z"
    - latency: 1.775036ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T12:33:02Z"
    - latency: 808.965µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T12:32:02Z"
    - latency: 2.19451ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T12:32:02Z"
    - latency: 1.116136ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T12:31:02Z"
    - latency: 1.75978ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T12:31:02Z"
    - latency: 1.196784ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T12:30:02Z"
    - latency: 1.705436ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T12:30:02Z"
    - latency: 749.814µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T12:29:02Z"
    - latency: 2.256119ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T12:29:02Z"
kind: List
metadata:
  resourceVersion: ""