Skip to content

Request to provide an option for s2iruns history limit #159

Description

@JohnNiang

Why?

As we run s2i builder frequently, more and more s2irun records and related ConfigMap remain.

image

2f4bb9d6858533373ecdc44501c016d6_

So I request to provide successfulS2irunsHistoryLimit and failedS2irunsHistoryLimit options into s2ibuilder CRD to limit the record of s2iruns history.

apiVersion: devops.kubesphere.io/v1alpha1
kind: S2iBuilder
metadata:
  name: myhalo-latest-qcd
  namespace: my-project
spec:
  config:
+   successfulS2irunsHistoryLimit: 10
+   failedS2irunsHistoryLimit: 1
    buildVolumes:
    - s2i_java_cache:/tmp/artifacts
    builderImage: kubesphere/java-8-centos7:v2.1.0
    builderPullPolicy: if-not-present
    export: true
    imageName: johnniang/myhalo
    isBinaryURL: true
    outputBuildResult: true
    pushAuthentication:
      secretRef:
        name: dockerhub-id
    revisionId: master
    runtimeArtifacts:
    - source: /deployments
    runtimeImage: kubesphere/java-8-runtime:v2.1.0
    sourceUrl: http://ks-apiserver.kubesphere-system.svc/kapis/devops.kubesphere.io/v1alpha2/namespaces/my-project/s2ibinaries/halo-1-4-13-jar37ev/file/halo-1.4.13.jar
    tag: latest

/kind feature

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions