Skip to main content
Flexible Top Header

I would love to get the community’s thoughts on this topic.

When working with Edge Service Points and various Edge services such DNS Resolver Service (DRS), Identity, Discovery etc, do you prefer to manage services and more specifically updates to services individually or would much rather prefer that the service updates be bundled inside the Service Point update (somewhat similar to BDDS and BIND/DHCPD package versions)?

Since the launch of Service Points v4 we allow services to be independently deployed and upgraded as long as the service point version allows for that specific service version to run. As more services are added, is it getting complex to manage them individually?

 

If you have another view on this please reply to this post. Looking forward to responses! :D

It depends on how to handle CVE’s when they come up and how a specific CVE effects the deployed host. In some cases the CVE effects packages, however there are CVE’s the effect OS level items as well. It would be great to update services but not sure if that can be done that way all the time

 

 It would be great to update services but not sure if that can be done that way all the time

 

Today, with every Edge release we include updates to all packages automatically to fix any security updates based on the development cut-off date (which is usually 4 weeks from GA date). I can also imagine there could be Service Point patches that only patch CVEs and other known issues that can be applied out of band. 

Also to note, not every SP release will need to have a new version of every service. It will likely be whichever service has bugs, feature, security updates etc. and/or service point - that is presented as one single SP update such as 25.2.1 → 25.2.2 (if it only contains minor/security fixes) or 25.3.0 if it has major features.

 

 

I would prefer to update independently, I think that’s more flexible.

Reply


Terms & ConditionsCookie settings