Github user vanzin commented on a diff in the pull request:

    https://github.com/apache/spark/pull/21669#discussion_r223516515
  
    --- Diff: 
resource-managers/kubernetes/core/src/main/scala/org/apache/spark/deploy/k8s/features/hadooputils/HadoopBootstrapUtil.scala
 ---
    @@ -0,0 +1,238 @@
    +/*
    + * Licensed to the Apache Software Foundation (ASF) under one or more
    + * contributor license agreements.  See the NOTICE file distributed with
    + * this work for additional information regarding copyright ownership.
    + * The ASF licenses this file to You under the Apache License, Version 2.0
    + * (the "License"); you may not use this file except in compliance with
    + * the License.  You may obtain a copy of the License at
    + *
    + *    http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +package org.apache.spark.deploy.k8s.features.hadooputils
    +
    +import java.io.File
    +
    +import scala.collection.JavaConverters._
    +
    +import com.google.common.base.Charsets
    +import com.google.common.io.Files
    +import io.fabric8.kubernetes.api.model._
    +
    +import org.apache.spark.SparkException
    +import org.apache.spark.deploy.k8s.Constants._
    +import org.apache.spark.deploy.k8s.SparkPod
    +
    +private[spark] object HadoopBootstrapUtil {
    +
    +   /**
    +    * Mounting the DT secret for both the Driver and the executors
    +    *
    +    * @param dtSecretName Name of the secret that stores the Delegation 
Token
    +    * @param dtSecretItemKey Name of the Item Key storing the Delegation 
Token
    +    * @param userName Name of the SparkUser to set SPARK_USER
    +    * @param maybeFileLocation Optional Location of the krb5 file
    +    * @param newKrb5ConfName Optional location of the ConfigMap for Krb5
    +    * @param maybeKrb5ConfName Optional name of ConfigMap for Krb5
    +    * @param pod Input pod to be appended to
    +    * @return a modified SparkPod
    +    */
    +  def bootstrapKerberosPod(
    +    dtSecretName: String,
    +    dtSecretItemKey: String,
    +    userName: String,
    +    maybeFileLocation: Option[String],
    +    newKrb5ConfName: String,
    +    maybeKrb5ConfName: Option[String],
    +    pod: SparkPod) : SparkPod = {
    +
    +    val maybePreConfigMapVolume = maybeKrb5ConfName.map { kconf =>
    +      new VolumeBuilder()
    +        .withName(KRB_FILE_VOLUME)
    +        .withNewConfigMap()
    +          .withName(kconf)
    +          .endConfigMap()
    +        .build() }
    +
    +    val maybeCreateConfigMapVolume = maybeFileLocation.map {
    +      fileLocation =>
    +      val krb5File = new File(fileLocation)
    +      val fileStringPath = krb5File.toPath.getFileName.toString
    +      new VolumeBuilder()
    +        .withName(KRB_FILE_VOLUME)
    +        .withNewConfigMap()
    +          .withName(newKrb5ConfName)
    +          .withItems(new KeyToPathBuilder()
    +            .withKey(fileStringPath)
    +            .withPath(fileStringPath)
    +            .build())
    +          .endConfigMap()
    +        .build() }
    +
    +    // Breaking up Volume Creation for clarity
    +    val configMapVolume =
    +      maybePreConfigMapVolume.getOrElse(
    +        maybeCreateConfigMapVolume.getOrElse(
    +          throw new SparkException(
    +            "Must specify krb5 file locally or via ConfigMap")
    --- End diff --
    
    Fits in previous line.
    
    But isn't this check already performed in `KerberosConfDriverFeatureStep`? 
Feels like you could avoid this extra check here somehow.


---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to