我可以在Kubernetes中将YAML代码部署为没有YAML文件的文件吗

问题描述

通过使用kubectl apply或使用helm install一次部署所有YAML文件，可以轻松地在Kubernetes中部署YAML文件，但是我正在寻找一种方式来部署YAML文件而不实际创建文件并直接通过nodeJS代码进行部署

我现在正在做什么：

我能够部署由我的nodeJS代码创建的YAML文件，该代码首先创建将其解析为YAML的JSON对象，然后生成其YAML文件，并且相同的代码也能够部署这些文件。

我需要什么：

我希望能够直接部署YAML代码而不创建其YAML文件。

解决方法

要从命令行申请，请使用：

node-js-generate-yaml-command | kubectl apply -f -

或者直接从代码中使用kubectl javascript客户端https://github.com/kubernetes-client/javascript

kubectl apply的示例可在此处https://github.com/kubernetes-client/javascript/blob/master/examples/typescript/apply/apply-example.ts

import * as k8s from '@kubernetes/client-node';
import * as fs from 'fs';
import * as yaml from 'js-yaml';
import { promisify } from 'util';

/**
 * Replicate the functionality of `kubectl apply`.  That is,create the resources defined in the `specFile` if they do
 * not exist,patch them if they do exist.
 *
 * @param specPath File system path to a YAML Kubernetes spec.
 * @return Array of resources created
 */
export async function apply(specPath: string): Promise<k8s.KubernetesObject[]> {
    const kc = new k8s.KubeConfig();
    kc.loadFromDefault();
    const client = k8s.KubernetesObjectApi.makeApiClient(kc);
    const fsReadFileP = promisify(fs.readFile);
    const specString = await fsReadFileP(specPath,'utf8');
    const specs: k8s.KubernetesObject[] = yaml.safeLoadAll(specString);
    const validSpecs = specs.filter((s) => s && s.kind && s.metadata);
    const created: k8s.KubernetesObject[] = [];
    for (const spec of validSpecs) {
        // this is to convince the old version of TypeScript that metadata exists even though we already filtered specs
        // without metadata out
        spec.metadata = spec.metadata || {};
        spec.metadata.annotations = spec.metadata.annotations || {};
        delete spec.metadata.annotations['kubectl.kubernetes.io/last-applied-configuration'];
        spec.metadata.annotations['kubectl.kubernetes.io/last-applied-configuration'] = JSON.stringify(spec);
        try {
            // try to get the resource,if it does not exist an error will be thrown and we will end up in the catch
            // block.
            await client.read(spec);
            // we got the resource,so it exists,so patch it
            const response = await client.patch(spec);
            created.push(response.body);
        } catch (e) {
            // we did not get the resource,so it does not exist,so create it
            const response = await client.create(spec);
            created.push(response.body);
        }
    }
    return created;
}

kubectl kubernetes