PTP Status Reporting via Custom Resource Conditions

[aneeshkp]

PTP: add PtpConfig status conditions API, helper, and RBAC for operand updates
Introduces status.ptpStatus.conditions[] on PtpConfig to expose runtime health/state per profile and active config file.
Adds a small helper API for operands (linuxptp-daemon, cloud-event-proxy) to upsert conditions via the status subresource.
Wires RBAC so linuxptp-daemon can update PtpConfig status.
Documents the schema and examples in README.

cond := ptpv1.PtpCondition{
Type: ptpv1.ConditionPTP4lRunning,
Profile: "GM-Profile-A",
Filename: "ptp4l.0.config",
Status: corev1.ConditionTrue,
Reason: "Started",
Message: "ptp4l is running",
LastUpdateTime: metav1.Now(),
}
_ = ptpstatus.UpsertPtpCondition(ctx, cs, "openshift-ptp", "default", cond)

Te operand can import the API call call this to update (RBAC are updated for linuxptp-daemon pods)

import (
corev1 "k8s.io/api/core/v1"
metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
"k8s.io/client-go/rest"

ptpv1 "github.com/k8snetworkplumbingwg/ptp-operator/api/v1"
clientset "github.com/k8snetworkplumbingwg/ptp-operator/pkg/client/clientset/versioned"
ptpstatus "github.com/k8snetworkplumbingwg/ptp-operator/pkg/status"
)

cfg, _ := rest.InClusterConfig()
cs, _ := clientset.NewForConfig(cfg)
_ = ptpstatus.UpsertPtpCondition(ctx, cs, "openshift-ptp", "default", ptpv1.PtpCondition{
Type: ptpv1.ConditionPTP4lRunning,
Profile: "GM-Profile-A",
Filename: "ptp4l.0.config",
Status: corev1.ConditionTrue,
Reason: "Started",
Message: "ptp4l is running",
LastUpdateTime: metav1.Now(),
})

[nocturnalastro]

Do we just want to do N conditions or should One of the same type replace it e.g if PTP4L is no longer running I would expect the running condition to be removed.

[aneeshkp]

hmm, I think we thought of replacing same kind , but same kind means we need to match with conditionType and other paramters file profile name and file name , to support multiple profiles

[aneeshkp]

if c.Type == cond.Type && c.Profile == cond.Profile && c.Filename == cond.Filename && c.Process == cond.Process {
*c = cond
updated = true
break
}

[josephdrichard]

So if one process (e.g. ptp4l) has too many statuses, we won't see detail from other processes such as ts2phc if it didn't report more recently than the last 100 ptp4l?

[aneeshkp]

good point , i should filter them by processname , will add that process name + profile name + file name (ptp4l.0.config )

[aneeshkp]

fixed , now upsert by composite key (type, profile, filename, process), so repeated ptp4l updates overwrite the same entry instead of appending. They won’t evict ts2phc, etc.

[aneeshkp]

now only if we have 100 distinct keys then we evict

[nocturnalastro]

/lgtm

[nocturnalastro]

Should gpspipe and gpsd be added here?

[josephdrichard]

What would this look like on daemon side?