Mid Server Architecture for Discovery, Event, Orchestration, Integration - How many do we need

[Curtis2]

We are looking to refresh our mid-server infrastructure and are considering a Kubernetes containerized structure.

We have two Data Centers in the US, two in the UK.

Challenges:  I don't really know anything about Kubernetes as I am an old school infrastructure guy use to working with 'cold iron' I can lay my hands on.

One of the questions I have is around the validation process for a new mid server.  If a new pod is spun up from a docker image, is there a way to automate the validation of the mid server?

Suggestions?  Recommendations?

[Sohail Khilji]

Hi @Curtis2 ,

Before fully migrating your mid-server infrastructure to Kubernetes, consider starting with a small-scale PoC. Deploy a few mid-server pods in a Kubernetes environment, test their functionality, and evaluate the performance and scalability. Use the PoC phase to learn and iterate on your Kubernetes setup.

[Pratiksha]

Hi @Curtis2,

Here you can learn deploying mid server in k8 https://www.servicenow.com/community/itom-articles/deploying-a-containerized-mid-server-in-a-kuberne...

https://www.youtube.com/watch?v=59NY8qbdcjc

I am hoping with validation you mean validating the mid server. It's a one time thing. So it's easy to validate directly from instance related list rather thinking for automation. 

Regards,

Pratiksha Khandelwal

[Curtis2]

Yes, that is what is meant by "validation."

If we have to manually validate a mid pod then we feel the value of being able to dynamically spin up new pods at needs is lost and therefore we see little value in pod mids.

[Pratiksha]

https://www.servicenow.com/community/now-platform-forum/validate-mid-server-via-api/m-p/1208790

Check the above thread it will help.