BookmarkSubscribeRSS Feed
EyalGonen
Lapis Lazuli | Level 10

Hi experts,

 

I need to deploy SAS Viya4 on AWS. The designated VPC does have access to the public Internet but only via a forward proxy which is accessed via HTTPS and its certificate is signed by a customer's CA. According to the customer the EKS nodes can access "cr.sas.com" to pull SAS docker images but they say that we need two things for this to work:

 

1. To make EKS (nodes? kubelet?) go through the forward proxy to reach "cr.sas.com".

2. Import the forward proxy's CA chain to EKS (to the nodes? kubelet?) otherwise TLS communication with the proxy will fail.

 

Anyone has experience doing something like this?

1 REPLY 1
gwootton
SAS Super FREQ
I think you'd need to set the HTTPS_PROXY environment variable for the container daemon (docker/containerd)

I found this article that seems to describe the process:
https://repost.aws/knowledge-center/eks-http-proxy-containerd-automation

Another option would be to use mirror manager and pointing to an Elastic Container Registry instead of cr.sas.com.
--
Greg Wootton | Principal Systems Technical Support Engineer

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 1 reply
  • 319 views
  • 1 like
  • 2 in conversation