fix(provider/kubernetes): Do not raise exception for named port in tcpSocket probes

[dtan4]

If named port is given as tcpSocket liveness/readiness probe, do not raise any exception and warn that only.

When a Kubernetes resource uses named port in its tcpSocket liveness/readiness probe, clouddriver raises java.lang.NumberFormatException. Clouddriver tries to parse port name redis as integer.

apiVersion: v1
items:
- apiVersion: apps/v1
  kind: StatefulSet
  metadata:
   ...
  spec:
    ...
    serviceName: redis
    template:
      metadata:
        name: redis
      spec:
        containers:
        - args:
          ...
          livenessProbe:
            failureThreshold: 3
            initialDelaySeconds: 30
            periodSeconds: 10
            successThreshold: 1
            tcpSocket:
              port: redis # <================================
            timeoutSeconds: 5
          name: redis
          ports:
          - containerPort: 6379
            name: redis
            protocol: TCP

java.lang.NumberFormatException: For input string: "redis"
        at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) ~[na:1.8.0_151]
        at java.lang.Integer.parseInt(Integer.java:580) ~[na:1.8.0_151]
        at java.lang.Integer.valueOf(Integer.java:766) ~[na:1.8.0_151]
        at org.codehaus.groovy.runtime.StringGroovyMethods.toInteger(StringGroovyMethods.java:3312) ~[groovy-all-2.4.12.jar:2.4.12]
        at org.codehaus.groovy.runtime.dgm$1160.invoke(Unknown Source) ~[groovy-all-2.4.12.jar:2.4.12]
        at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:274) ~[groovy-all-2.4.12.jar:2.4.12]
        at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:56) ~[groovy-all-2.4.12.jar:2.4.12]
        at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:117) ~[groovy-all-2.4.12.jar:2.4.12]
        at com.netflix.spinnaker.clouddriver.kubernetes.v1.api.KubernetesClientApiConverter.fromTcpSocketAction(KubernetesClientApiConverter.groovy:315) ~[clouddriver-kubernetes-1.775.0-SNAPSHOT.jar:1.775.0-SNAPSHOT]
        at com.netflix.spinnaker.clouddriver.kubernetes.v1.api.KubernetesClientApiConverter$fromTcpSocketAction$0.callStatic(Unknown Source) ~[na:na]
        at com.netflix.spinnaker.clouddriver.kubernetes.v1.api.KubernetesClientApiConverter.fromV1Probe(KubernetesClientApiConverter.groovy:338) ~[clouddriver-kubernetes-1.775.0-SNAPSHOT.jar:1.775.0-SNAPSHOT]
        at com.netflix.spinnaker.clouddriver.kubernetes.v1.api.KubernetesClientApiConverter$fromV1Probe.callStatic(Unknown Source) ~[na:na]
        at com.netflix.spinnaker.clouddriver.kubernetes.v1.api.KubernetesClientApiConverter.fromContainer(KubernetesClientApiConverter.groovy:197) ~[clouddriver-kubernetes-1.775.0-SNAPSHOT.jar:1.775.0-SNAPSHOT]

Clouddriver does the same behavior for named port in httpGet probe. I followed the implementation.

[lwander]

What happens if you try to use the Spinnaker UI to clone a server group that uses a named port?

[dtan4]

I tried the behavior with the below steps,

1. Deploy ReplicaSet (new server group) with named ports
2. Clone created server group to new one

then confirmed that all named ports were cloned properly with name.

[lwander]

Sweet!

[lwander]

Closes spinnaker/spinnaker#1210