apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:50:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-179-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-179.ec2.internal
      uid: c2031520-3726-4e1c-ba5b-7f00ddd4d042
    resourceVersion: "14856"
    uid: fd617e4c-4443-4591-bc9c-658564d89e61
  spec:
    sourcePod: network-check-source-7d88cb55d8-7szh8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:57:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.299506ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:57:42Z"
    - latency: 983.343µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:56:42Z"
    - latency: 1.198892ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:55:42Z"
    - latency: 1.200468ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:54:42Z"
    - latency: 860.328µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:53:42Z"
    - latency: 773.385µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:52:42Z"
    - latency: 1.058939ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:51:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:50:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-179-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-179.ec2.internal
      uid: c2031520-3726-4e1c-ba5b-7f00ddd4d042
    resourceVersion: "16583"
    uid: 6c9c2fe7-74e7-477b-a5bb-b0e5988963df
  spec:
    sourcePod: network-check-source-7d88cb55d8-7szh8
    targetEndpoint: a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:56:42Z"
      message: 'load-balancer-api-external: tcp connection to a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.869239ms
      message: 'load-balancer-api-external: tcp connection to a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:02:42Z"
    - latency: 7.531565ms
      message: 'load-balancer-api-external: resolved host name a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:02:42Z"
    - latency: 6.125324ms
      message: 'load-balancer-api-external: tcp connection to a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:01:42Z"
    - latency: 7.72967ms
      message: 'load-balancer-api-external: resolved host name a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:01:42Z"
    - latency: 5.016953ms
      message: 'load-balancer-api-external: tcp connection to a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:00:42Z"
    - latency: 8.739254ms
      message: 'load-balancer-api-external: resolved host name a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:00:42Z"
    - latency: 4.93042ms
      message: 'load-balancer-api-external: tcp connection to a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:59:42Z"
    - latency: 9.66982ms
      message: 'load-balancer-api-external: resolved host name a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:59:42Z"
    - latency: 5.713292ms
      message: 'load-balancer-api-external: tcp connection to a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:58:42Z"
    - latency: 7.658277ms
      message: 'load-balancer-api-external: resolved host name a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:58:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:50:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-179-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-179.ec2.internal
      uid: c2031520-3726-4e1c-ba5b-7f00ddd4d042
    resourceVersion: "16584"
    uid: 7335272a-b3b7-4208-a1e2-9a8d6668172f
  spec:
    sourcePod: network-check-source-7d88cb55d8-7szh8
    targetEndpoint: a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:56:42Z"
      message: 'load-balancer-api-internal: tcp connection to a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.813469ms
      message: 'load-balancer-api-internal: tcp connection to a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:02:42Z"
    - latency: 7.647187ms
      message: 'load-balancer-api-internal: resolved host name a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:02:42Z"
    - latency: 6.143491ms
      message: 'load-balancer-api-internal: tcp connection to a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:01:42Z"
    - latency: 7.696745ms
      message: 'load-balancer-api-internal: resolved host name a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:01:42Z"
    - latency: 5.07717ms
      message: 'load-balancer-api-internal: tcp connection to a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:00:42Z"
    - latency: 8.840735ms
      message: 'load-balancer-api-internal: resolved host name a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:00:42Z"
    - latency: 4.821242ms
      message: 'load-balancer-api-internal: tcp connection to a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:59:42Z"
    - latency: 9.689534ms
      message: 'load-balancer-api-internal: resolved host name a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:59:42Z"
    - latency: 5.713032ms
      message: 'load-balancer-api-internal: tcp connection to a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:58:42Z"
    - latency: 7.818211ms
      message: 'load-balancer-api-internal: resolved host name a82cf27899e0f41c99f160e1637fb233-1c647be181cb00ef.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:58:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:50:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-179-to-network-check-target-ip-10-0-131-179
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-179.ec2.internal
      uid: c2031520-3726-4e1c-ba5b-7f00ddd4d042
    resourceVersion: "14852"
    uid: f6d67333-715b-4e03-aa11-6570eb39b21f
  spec:
    sourcePod: network-check-source-7d88cb55d8-7szh8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:57:42Z"
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.376514ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:57:42Z"
    - latency: 959.802µs
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:56:42Z"
    - latency: 1.369816ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:55:42Z"
    - latency: 976.847µs
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:54:42Z"
    - latency: 947.487µs
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:53:42Z"
    - latency: 1.064363ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:52:42Z"
    - latency: 1.151969ms
      message: 'network-check-target-ip-10-0-131-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:51:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:50:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-179-to-network-check-target-ip-10-0-138-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-179.ec2.internal
      uid: c2031520-3726-4e1c-ba5b-7f00ddd4d042
    resourceVersion: "14854"
    uid: 24e148a5-76f5-46e1-90d5-7b92b17df10b
  spec:
    sourcePod: network-check-source-7d88cb55d8-7szh8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:57:42Z"
      message: 'network-check-target-ip-10-0-138-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.212492ms
      message: 'network-check-target-ip-10-0-138-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:57:42Z"
    - latency: 2.308719ms
      message: 'network-check-target-ip-10-0-138-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:56:42Z"
    - latency: 2.430336ms
      message: 'network-check-target-ip-10-0-138-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:55:42Z"
    - latency: 2.319814ms
      message: 'network-check-target-ip-10-0-138-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:54:42Z"
    - latency: 2.334015ms
      message: 'network-check-target-ip-10-0-138-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:53:42Z"
    - latency: 1.915378ms
      message: 'network-check-target-ip-10-0-138-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:52:42Z"
    - latency: 2.280308ms
      message: 'network-check-target-ip-10-0-138-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:51:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:50:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-179-to-network-check-target-ip-10-0-138-44
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-179.ec2.internal
      uid: c2031520-3726-4e1c-ba5b-7f00ddd4d042
    resourceVersion: "14853"
    uid: 812b5ac5-efe2-4e84-b9f0-09f8727aeaac
  spec:
    sourcePod: network-check-source-7d88cb55d8-7szh8
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:57:42Z"
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.818651ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:57:42Z"
    - latency: 2.069581ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:56:42Z"
    - latency: 2.187635ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:55:42Z"
    - latency: 2.038561ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:54:42Z"
    - latency: 1.86116ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:53:42Z"
    - latency: 1.980153ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:52:42Z"
    - latency: 1.909135ms
      message: 'network-check-target-ip-10-0-138-44: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:51:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:50:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-179-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-179.ec2.internal
      uid: c2031520-3726-4e1c-ba5b-7f00ddd4d042
    resourceVersion: "16581"
    uid: 99168681-4488-4834-9576-4eaae6848be5
  spec:
    sourcePod: network-check-source-7d88cb55d8-7szh8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:56:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.085381ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:02:42Z"
    - latency: 2.08168ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:02:42Z"
    - latency: 976.781µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:01:42Z"
    - latency: 2.02714ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:01:42Z"
    - latency: 906.028µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:00:42Z"
    - latency: 1.778674ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:00:42Z"
    - latency: 1.349046ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:59:42Z"
    - latency: 2.096894ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:59:42Z"
    - latency: 1.13324ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:58:42Z"
    - latency: 2.094969ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:58:42Z"
kind: List
metadata:
  resourceVersion: ""